From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Hari Bathini
<hbathini-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: ananth-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org,
rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org,
aravinda-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
kernel-6AxghH7DbtA@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org
Subject: Re: [RFC PATCH v2 0/3] perf/tracefs: Container-aware tracing support
Date: Wed, 03 Aug 2016 21:59:02 -0500 [thread overview]
Message-ID: <87twf1ck95.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <146965470618.23765.7329786743211962695.stgit-2ivJzYymj6EA+286u2LMdEEOCMrvLtNR@public.gmane.org> (Hari Bathini's message of "Thu, 28 Jul 2016 02:57:16 +0530")
Hari Bathini <hbathini-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> writes:
> This RFC patch set supports filtering container specific events
> when perf tool is executed inside a container. The patches apply
> cleanly on v4.7.0-rc7
>
> Changes from v1:
> 1/3. Revived earlier approach[1] with cgroup namespace instead
> of pid namespace
> 2/3. New patch that adds instance support for uprobe events in
> tracefs filesystem
> 3/3. New patch that adds "newinstance" mount option for tracefs
> filesystem
"newinstace" ick no.
I see no justification anywhere why the perf cgroup is not enough for
this.
Eric
next parent reply other threads:[~2016-08-04 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <146965470618.23765.7329786743211962695.stgit@hbathini.in.ibm.com>
[not found] ` <146965470618.23765.7329786743211962695.stgit-2ivJzYymj6EA+286u2LMdEEOCMrvLtNR@public.gmane.org>
2016-08-04 2:59 ` Eric W. Biederman [this message]
[not found] ` <87twf1ck95.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-08-04 14:48 ` [RFC PATCH v2 0/3] perf/tracefs: Container-aware tracing support Aravinda Prasad
[not found] ` <57A355C1.4090004@linux.vnet.ibm.com>
[not found] ` <57A355C1.4090004-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-08-04 18:27 ` Eric W. Biederman
[not found] ` <87h9b01ja2.fsf@x220.int.ebiederm.org>
[not found] ` <87h9b01ja2.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-08-04 19:11 ` Aravinda Prasad
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=87twf1ck95.fsf@x220.int.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=ananth-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=aravinda-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org \
--cc=hbathini-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=kernel-6AxghH7DbtA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.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