mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: LKML <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"jolsa@redhat.com" <jolsa@redhat.com>
Cc: Kernel Team <Kernel-team@fb.com>, Ephraim Park <ephiepark@fb.com>
Subject: Re: [PATCH v2] perf: update perf_cgroup time for ancestor cgroup(s)
Date: Wed, 14 Mar 2018 21:30:53 +0000	[thread overview]
Message-ID: <B3C675EC-C458-4A15-B91D-5B17E3D6319C@fb.com> (raw)
In-Reply-To: <20180312165943.1057894-1-songliubraving@fb.com>

Dear Peter, 

Could you please share your comments/suggestions on this patch? We would
like to fix this issue in our kernel, as we are using perf events with 
nested cgroups. 

Thanks,
Song

> On Mar 12, 2018, at 9:59 AM, Song Liu <songliubraving@fb.com> 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>
> ---
> kernel/events/core.c | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 5789810..6f015ff 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -724,9 +724,14 @@ static inline void __update_cgrp_time(struct perf_cgroup *cgrp)
> 
> static inline void update_cgrp_time_from_cpuctx(struct perf_cpu_context *cpuctx)
> {
> -	struct perf_cgroup *cgrp_out = cpuctx->cgrp;
> -	if (cgrp_out)
> -		__update_cgrp_time(cgrp_out);
> +	struct perf_cgroup *cgrp = cpuctx->cgrp;
> +	struct cgroup_subsys_state *css;
> +
> +	if (cgrp)
> +		for (css = &cgrp->css; css; css = css->parent) {
> +			cgrp = container_of(css, struct perf_cgroup, css);
> +			__update_cgrp_time(cgrp);
> +		}
> }
> 
> static inline void update_cgrp_time_from_event(struct perf_event *event)
> @@ -754,6 +759,7 @@ perf_cgroup_set_timestamp(struct task_struct *task,
> {
> 	struct perf_cgroup *cgrp;
> 	struct perf_cgroup_info *info;
> +	struct cgroup_subsys_state *css;
> 
> 	/*
> 	 * ctx->lock held by caller
> @@ -764,8 +770,12 @@ perf_cgroup_set_timestamp(struct task_struct *task,
> 		return;
> 
> 	cgrp = perf_cgroup_from_task(task, ctx);
> -	info = this_cpu_ptr(cgrp->info);
> -	info->timestamp = ctx->timestamp;
> +
> +	for (css = &cgrp->css; css; css = css->parent) {
> +		cgrp = container_of(css, struct perf_cgroup, css);
> +		info = this_cpu_ptr(cgrp->info);
> +		info->timestamp = ctx->timestamp;
> +	}
> }
> 
> static DEFINE_PER_CPU(struct list_head, cgrp_cpuctx_list);
> -- 
> 2.9.5
> 

  reply	other threads:[~2018-03-14 21:31 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 [this message]
2018-03-16 14:24 ` Peter Zijlstra
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=B3C675EC-C458-4A15-B91D-5B17E3D6319C@fb.com \
    --to=songliubraving@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=ephiepark@fb.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    /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

all inboxes | Powered by JetHome®