From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: linux-kernel@vger.kernel.org, jolsa@redhat.com,
kernel-team@fb.com, ephiepark@fb.com
Subject: Re: [PATCH v2] perf: update perf_cgroup time for ancestor cgroup(s)
Date: Fri, 16 Mar 2018 15:24:47 +0100 [thread overview]
Message-ID: <20180316142447.GA4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180312165943.1057894-1-songliubraving@fb.com>
On Mon, Mar 12, 2018 at 09:59:43AM -0700, Song Liu wrote:
> When a perf_event is attached to parent cgroup, it should count events
> for all children cgroups:
>
> parent_group <---- perf_event
> \
> - child_group <---- process(es)
>
> However, in our tests, we found this perf_event cannot report reliable
> results. Here is an example case:
>
> # create cgroups
> mkdir -p /sys/fs/cgroup/p/c
> # start perf for parent group
> perf stat -e instructions -G "p"
>
> # on another console, run test process in child cgroup:
> stressapptest -s 2 -M 1000 & echo $! > /sys/fs/cgroup/p/c/cgroup.procs
>
> # after the test process is done, stop perf in the first console shows
>
> <not counted> instructions p
>
> The instruction should not be "not counted" as the process runs in the
> child cgroup.
>
> We found this is because perf_event->cgrp and cpuctx->cgrp are not
> identical, thus perf_event->cgrp are not updated properly.
>
> This patch fixes this by updating perf_cgroup properly for ancestor
> cgroup(s).
>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> Reported-by: Ephraim Park <ephiepark@fb.com>
Yeah, that looks about right, Thanks!
next prev parent reply other threads:[~2018-03-16 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 16:59 Song Liu
2018-03-14 21:30 ` Song Liu
2018-03-16 14:24 ` Peter Zijlstra [this message]
2018-03-20 11:18 ` [tip:perf/urgent] perf/cgroup: Fix child event counting bug tip-bot for Song Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180316142447.GA4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ephiepark@fb.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=songliubraving@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome