[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1365474213-13354-1-git-send-email-tj@kernel.org>
Date: Mon, 8 Apr 2013 19:23:30 -0700
From: Tejun Heo <tj@...nel.org>
To: mingo@...hat.com
Cc: a.p.zijlstra@...llo.nl, paulus@...ba.org, acme@...stprotocols.net,
eranian@...gle.com, namhyung.kim@....com, lizefan@...wei.com,
mhocko@...e.cz, kamezawa.hiroyu@...fujitsu.com,
cgroups@...r.kernel.org, containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: [PATCHSET] perf, cgroup: implement hierarchy support for perf_event controller
perf_event cgroup controller is one of the remaining few with broken
hierarchy support. It turns out it's pretty easy to implement - the
only thing necessary is making perf_cgroup_match() return %true also
when the cgroup of the current task is a descendant of the event's
cgroup. This patchset implements cgroup_is_descendant() and uses it
to implement hierarchy support in perf_event controller.
This patchset contains the following three patches.
0001-cgroup-make-sure-parent-won-t-be-destroyed-before-it.patch
0002-cgroup-implement-cgroup_is_descendant.patch
0003-perf-make-perf_event-cgroup-hierarchical.patch
The patches are also available in the following git branch, which is
based on top of cgroup/for-3.10. It's currently based on top of
cgroup/for-3.10 as the first patch causes non-trivial conflict with it
otherwise, which is not difficult to resolve but still nice to avoid
anyway.
Li, Michal, I picked the first two patches from Li's memcg patchset.
Can we push the first two through cgroup/for-3.10 and put the rest in
-mm?
Ingo, how should these be routed?
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git perf_event-hierarchy-support
diffstat follows, thanks.
include/linux/cgroup.h | 1 +
kernel/cgroup.c | 30 ++++++++++++++++++++++++++++++
kernel/events/core.c | 24 ++++++++++++++++--------
3 files changed, 47 insertions(+), 8 deletions(-)
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists