Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <2db9fab4-0aff-b8b0-5012-13556ea496af@linux.intel.com>
Date:   Mon, 31 Jan 2022 17:16:14 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.1
Subject: Re: [PATCH 0/3] Handle chroot tasks properly (v1)
Content-Language: en-US
To:     Namhyung Kim <namhyung@kernel.org>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Jiri Olsa <jolsa@redhat.com>
Cc:     Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Ian Rogers <irogers@google.com>
References: <20220128203950.3371061-1-namhyung@kernel.org>
From:   Andi Kleen <ak@linux.intel.com>
In-Reply-To: <20220128203950.3371061-1-namhyung@kernel.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 1/28/2022 12:39 PM, Namhyung Kim wrote:
> Hello,
>
> I found that perf tools don't work well with tasks in a chroot.  The
> filenames in MMAP record are from the root directory of the task so
> it's different than what it sees from outside.


While that's a real problem, and for chroot it can be fixed, it's much 
more complicated for the more complex container namespace case with 
custom mounts, including loop back, etc.

It seems it really need some kind of agent to handle all cases. For 
example the agent could understand container metadata formats and then 
do the right thing.

-Andi