From: Lin Xiulei <linxiulei@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, Stephane Eranian <eranian@gmail.com>,
torvalds@linux-foundation.org, linux-perf-users@vger.kernel.org,
Brendan Gregg <brendan.d.gregg@gmail.com>,
yang_oliver@hotmail.com,
"leilei.lin" <leilei.lin@alibaba-inc.com>
Subject: Re: [PATCH RESEND v5] perf/core: Fix installing arbitrary cgroup event into cpu
Date: Mon, 12 Mar 2018 19:46:52 +0800 [thread overview]
Message-ID: <CALPjY3mx37seF_=S90B_2=zq_UjEiQSZSKuyjSDQ0ci7ytc0LQ@mail.gmail.com> (raw)
In-Reply-To: <20180312075307.iut52znscixqcpag@gmail.com>
2018-03-12 15:53 GMT+08:00 Ingo Molnar <mingo@kernel.org>:
>
> * linxiulei@gmail.com <linxiulei@gmail.com> wrote:
>
>> /*
>> * Because cgroup events are always per-cpu events,
>> * this will always be called from the right CPU.
>> */
>
>> + /*
>> + * if only the cgroup is running on this cpu
>> + * and cpuctx->cgrp == NULL (otherwise it would've
>> + * been set with running cgroup), we put this cgroup
>> + * into cpu context. Or it would case mismatch in
>> + * following cgroup events at event_filter_match()
>> + */
>
> Beyond making sure that what you comment on makes sense, please also follow
> existing comment style, which I quoted above.
>
> There's 3 separate mistakes in that paragraph alone.
>
> Thanks,
>
> Ingo
Thank Ingo for pointing it out. though I'd try to follow it as
possible as I could. I wish I have somewhere to check style with
specific documents : )
+ /*
+ * We will set cpuctx->cgrp only if:
+ * 1) cpuctx->cgrp is NULL. Because cpuctx->cgrp was set
+ * correctly by sched_in(). We don't need to set it again.
+ * 2) cgroup related to this event is running on this CPU.
+ * Otherwise it will fail in event_filter_match()
+ */
Peter, did I explain that logic clearly and prove it right?
Regards
prev parent reply other threads:[~2018-03-12 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 9:36 [PATCH RESEND v5] perf/core: Fix installing arbitrary cgroup event into cpu linxiulei
2018-03-06 11:50 ` Peter Zijlstra
2018-03-07 11:19 ` Lin Xiulei
2018-03-12 12:24 ` Peter Zijlstra
2018-03-12 13:10 ` Lin Xiulei
2018-03-12 7:53 ` Ingo Molnar
2018-03-12 11:46 ` Lin Xiulei [this message]
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='CALPjY3mx37seF_=S90B_2=zq_UjEiQSZSKuyjSDQ0ci7ytc0LQ@mail.gmail.com' \
--to=linxiulei@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brendan.d.gregg@gmail.com \
--cc=eranian@gmail.com \
--cc=jolsa@redhat.com \
--cc=leilei.lin@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--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).