From: Li Zefan <lizf@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Menage <menage@google.com>,
balbir@linux.vnet.ibm.com, eranian@google.com,
linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org,
davem@davemloft.net, fweisbec@gmail.com,
perfmon2-devel@lists.sf.net, eranian@gmail.com,
robert.richter@amd.com, acme@redhat.com
Subject: Re: [RFC][PATCH] cgroup: Fix cgroup_subsys::exit callback
Date: Thu, 10 Feb 2011 10:04:57 +0800 [thread overview]
Message-ID: <4D5347C9.2030909@cn.fujitsu.com> (raw)
In-Reply-To: <1297160655.13327.92.camel@laptop>
(just came back from vacation)
>> How about if the exit callback was moved before the preceding
>> task_unlock()? Since I think the scheduler is still the only user of
>> the exit callback, redefining the locking semantics should be fine.
>
> Like the below? Both the perf and sched exit callback are fine with
> being called under task_lock afaict, but I haven't actually ran with
> lockdep enabled to see if I missed something.
>
This change should be fine.
...
> +
> + if (run_callbacks && need_forkexit_callback) {
> + /*
> + * modular subsystems can't use callbacks, so no need to lock
> + * the subsys array
> + */
> + for (i = 0; i < CGROUP_BUILTIN_SUBSYS_COUNT; i++) {
> + struct cgroup_subsys *ss = subsys[i];
> + if (ss->exit) {
> + struct cgroup *old_cgrp =
> + rcu_dereference_raw(cg->subsys[i])->cgroup;
> + struct cgroup *cgrp = task_cgroup(tsk, i);
> + ss->exit(ss, cgrp, old_cgrp, tsk);
Since both sched and perf won't use the 2 args @cgrp and @old_cgrp,
don't bother to change the ->exit interface?
> + }
> + }
> + }
> task_unlock(tsk);
> +
> if (cg)
> put_css_set_taskexit(cg);
> }
next prev parent reply other threads:[~2011-02-10 2:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 13:30 [PATCH 1/2] perf_events: add cgroup support (v8) Stephane Eranian
2011-01-20 14:39 ` Peter Zijlstra
2011-01-20 14:46 ` Stephane Eranian
2011-02-02 11:29 ` Peter Zijlstra
2011-02-02 11:50 ` Balbir Singh
2011-02-02 12:46 ` Peter Zijlstra
2011-02-02 19:02 ` Balbir Singh
2011-02-07 16:10 ` [RFC][PATCH] cgroup: Fix cgroup_subsys::exit callback Peter Zijlstra
2011-02-07 19:28 ` Paul Menage
2011-02-07 20:02 ` Peter Zijlstra
2011-02-07 21:21 ` Paul Menage
2011-02-08 10:24 ` Peter Zijlstra
2011-02-10 2:04 ` Li Zefan [this message]
2011-02-11 12:13 ` Peter Zijlstra
2011-02-14 4:32 ` Paul Menage
2011-02-16 13:46 ` [tip:perf/core] " tip-bot for Peter Zijlstra
2011-02-13 12:52 ` [RFC][PATCH] " Balbir Singh
2011-02-07 19:29 ` [PATCH 1/2] perf_events: add cgroup support (v8) Paul Menage
2011-02-07 20:09 ` Peter Zijlstra
2011-02-07 21:33 ` Paul Menage
2011-02-07 16:10 ` Peter Zijlstra
2011-02-07 20:30 ` Stephane Eranian
2011-02-08 22:31 ` Stephane Eranian
2011-02-09 9:47 ` Peter Zijlstra
2011-02-10 11:47 ` Stephane Eranian
2011-02-11 0:55 ` Li Zefan
2011-02-11 9:56 ` Stephane Eranian
2011-02-11 13:36 ` Stephane Eranian
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=4D5347C9.2030909@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=acme@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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