[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cj1RG0Do9TDSGpRScK+O0bYZ=EEwCdibScBkTbz=4f4Tw@mail.gmail.com>
Date: Wed, 25 Mar 2020 22:19:57 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Tejun Heo <tj@...nel.org>, Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCHSET 0/9] perf: Improve cgroup profiling (v6)
Hi Arnaldo,
On Wed, Mar 25, 2020 at 10:05 PM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> Em Wed, Mar 25, 2020 at 09:45:27PM +0900, Namhyung Kim escreveu:
> > Hello,
> >
> > This work is to improve cgroup profiling in perf. Currently it only
> > supports profiling tasks in a specific cgroup and there's no way to
> > identify which cgroup the current sample belongs to. So I added
> > PERF_SAMPLE_CGROUP to add cgroup id into each sample. It's a 64-bit
> > integer having file handle of the cgroup. And kernel also generates
> > PERF_RECORD_CGROUP event for new groups to correlate the cgroup id and
> > cgroup name (path in the cgroup filesystem). The cgroup id can be
> > read from userspace by name_to_handle_at() system call so it can
> > synthesize the CGROUP event for existing groups.
>
> Thanks for the refresh, I'll test this today and all going well push to
> Ingo soon,
Thanks for doing this!
Namhyung
Powered by blists - more mailing lists