From: Ingo Molnar <mingo@kernel.org>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf-event/cgroup: explicitly init the early_init field
Date: Tue, 22 Apr 2014 08:06:54 +0200 [thread overview]
Message-ID: <20140422060654.GB9133@gmail.com> (raw)
In-Reply-To: <1398144517-9496-1-git-send-email-nasa4836@gmail.com>
* Jianyu Zhan <nasa4836@gmail.com> wrote:
> For a cgroup subsystem who should init early, then it should carefully
> take care of the implementation of css_alloc, because it will be called
> before mm_init() setup the world.
>
> Luckily we don't, and we better explicitly assign the early_init field
> to 0, for document reason.
>
> Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
> ---
> kernel/events/core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index f83a71a..b3a8916 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8062,5 +8062,6 @@ struct cgroup_subsys perf_event_cgrp_subsys = {
> .css_free = perf_cgroup_css_free,
> .exit = perf_cgroup_exit,
> .attach = perf_cgroup_attach,
> + .early_init = 0,
How can that field ever be nonzero?
I.e. under what exact circumstances does this patch make sense?
Thanks,
Ingo
next prev parent reply other threads:[~2014-04-22 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 5:28 [PATCH] perf-event/cgroup: explicitly init the early_init field Jianyu Zhan
2014-04-22 6:06 ` Ingo Molnar [this message]
2014-04-22 6:42 ` Jianyu Zhan
2014-04-22 7:12 ` Jianyu Zhan
2014-04-22 9:31 ` Li Zefan
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=20140422060654.GB9133@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nasa4836@gmail.com \
--cc=paulus@samba.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