From: Jiri Olsa <jolsa@redhat.com>
To: linxiulei@gmail.com
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, tglx@linutronix.de,
eranian@gmail.com, torvalds@linux-foundation.org,
brendan.d.gregg@gmail.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, yang_oliver@hotmail.com,
jinli.zjl@alibaba-inc.com,
"leilei.lin" <leilei.lin@alibaba-inc.com>
Subject: Re: [PATCH RESEND v4] perf/core: Fix installing cgroup event into cpu
Date: Thu, 8 Feb 2018 16:36:48 +0100 [thread overview]
Message-ID: <20180208153648.GC12817@krava> (raw)
In-Reply-To: <20180208033344.71933-1-linxiulei@gmail.com>
On Thu, Feb 08, 2018 at 11:33:44AM +0800, linxiulei@gmail.com wrote:
> From: "leilei.lin" <leilei.lin@alibaba-inc.com>
>
> Do not install cgroup event into the CPU context and schedule it
> if the cgroup is not running on this CPU
>
> While there is no task of cgroup running specified CPU, current
> kernel still install cgroup event into CPU context that causes
> another cgroup event can't be installed into this CPU.
>
> This patch prevent scheduling events at __perf_install_in_context()
> and installing events at list_update_cgroup_event() if cgroup isn't
> running on specified CPU.
>
> Signed-off-by: leilei.lin <leilei.lin@alibaba-inc.com>
> ---
> v2: Set cpuctx->cgrp only if the same cgroup is running on this
> CPU otherwise following events couldn't be activated immediately
> v3: Enhance the comments and commit message
> v4: Adjust to config
>
> kernel/events/core.c | 50 +++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 37 insertions(+), 13 deletions(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 4df5b69..fd28d61 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -933,31 +933,41 @@ list_update_cgroup_event(struct perf_event *event,
> {
> struct perf_cpu_context *cpuctx;
> struct list_head *cpuctx_entry;
> + struct perf_cgroup *cgrp;
>
> if (!is_cgroup_event(event))
> return;
>
> - if (add && ctx->nr_cgroups++)
> - return;
> - else if (!add && --ctx->nr_cgroups)
> - return;
I might be missing something, but should this check stay on
the top regardles of the cgroup_is_descendant check below?
you could put NULL into cpuctx->cgrp on context with cgroup
event in the list
thanks,
jirka
> /*
> * Because cgroup events are always per-cpu events,
> * this will always be called from the right CPU.
> */
> cpuctx = __get_cpu_context(ctx);
> - cpuctx_entry = &cpuctx->cgrp_cpuctx_entry;
> - /* cpuctx->cgrp is NULL unless a cgroup event is active in this CPU .*/
> - if (add) {
> - struct perf_cgroup *cgrp = perf_cgroup_from_task(current, ctx);
> + cgrp = perf_cgroup_from_task(current, ctx);
>
> - list_add(cpuctx_entry, this_cpu_ptr(&cgrp_cpuctx_list));
> - if (cgroup_is_descendant(cgrp->css.cgroup, event->cgrp->css.cgroup))
> + /*
> + * if only the cgroup is running on this cpu,
> + * we put/remove this cgroup into cpu context.
> + * Or it would case mismatch in following cgroup
> + * events at event_filter_match()
> + */
> + if (cgroup_is_descendant(cgrp->css.cgroup, event->cgrp->css.cgroup)) {
> + if (add)
> cpuctx->cgrp = cgrp;
> - } else {
> - list_del(cpuctx_entry);
> - cpuctx->cgrp = NULL;
> + else
> + cpuctx->cgrp = NULL;
SNIP
next prev parent reply other threads:[~2018-02-08 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 3:33 [PATCH RESEND v4] perf/core: Fix installing cgroup event into cpu linxiulei
2018-02-08 15:36 ` Jiri Olsa [this message]
2018-02-09 1:52 ` Lin Xiulei
2018-02-09 10:11 ` Peter Zijlstra
2018-02-10 12:28 ` Lin Xiulei
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=20180208153648.GC12817@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brendan.d.gregg@gmail.com \
--cc=eranian@gmail.com \
--cc=jinli.zjl@alibaba-inc.com \
--cc=leilei.lin@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linxiulei@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yang_oliver@hotmail.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;
as well as URLs for NNTP newsgroup(s).