From: Tejun Heo <tj@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lizefan@huawei.com, hannes@cmpxchg.org, a.p.zijlstra@chello.nl,
mingo@redhat.com, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH REPOST 2/2] cgroup, perf_event: make perf_event controller work on cgroup2 hierarchy
Date: Mon, 30 Jan 2017 10:07:33 -0500 [thread overview]
Message-ID: <20170130150733.GA4568@htj.duckdns.org> (raw)
In-Reply-To: <20170130140541.GG9082@kernel.org>
Hello,
On Mon, Jan 30, 2017 at 11:05:41AM -0300, Arnaldo Carvalho de Melo wrote:
> > This was posted months ago and acked by Peter. I thought it was
> > applied but apparently wasn't. Peter asked Arnaldo whether the
> > userspace part looked which didn't get replied and that probably was
> > how it slipped through the crack.
> >
> > Peter, Arnanldo, how should we proceed? Should I route this through
> > the cgroup tree?
>
> It looks ok, haven't tested it tho. I don't have a problem for it to go
> thru the cgroup tree. The change is small and restrictred to cgroup
> glue in tools/perf/.
Alright, thanks. Will apply it to cgroup/for-4.11 in a couple days.
If there's any objection, please holler.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-01-30 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 22:12 [PATCHSET v2 cgroup/for-4.6] cgroup, perf_event: make perf_event work on v2 hierarchy Tejun Heo
2016-02-24 22:12 ` [PATCH 1/2] cgroup: implement cgroup_subsys->implicit_on_dfl Tejun Heo
2016-03-08 15:59 ` Tejun Heo
2016-02-24 22:12 ` [PATCH 2/2] cgroup, perf_event: make perf_event controller work on cgroup2 hierarchy Tejun Heo
2016-03-08 10:11 ` Peter Zijlstra
2017-01-29 19:35 ` [PATCH REPOST " Tejun Heo
2017-01-30 14:05 ` Arnaldo Carvalho de Melo
2017-01-30 15:07 ` Tejun Heo [this message]
2017-02-02 18:47 ` Tejun Heo
2016-03-03 15:06 ` [PATCHSET v2 cgroup/for-4.6] cgroup, perf_event: make perf_event work on v2 hierarchy Tejun Heo
2016-03-08 1:44 ` Tejun Heo
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=20170130150733.GA4568@htj.duckdns.org \
--to=tj@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.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).