From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hari Bathini <hbathini@linux.vnet.ibm.com>,
ast@fb.com, lkml <linux-kernel@vger.kernel.org>,
alexander.shishkin@linux.intel.com, mingo@redhat.com,
daniel@iogearbox.net, rostedt@goodmis.org,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
ebiederm@xmission.com, sargun@sargun.me,
Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
brendan.d.gregg@gmail.com, jolsa@redhat.com
Subject: Re: [PATCH v7 1/8] perf: add PERF_RECORD_NAMESPACES to include namespaces related info
Date: Wed, 1 Mar 2017 17:45:09 -0300 [thread overview]
Message-ID: <20170301204509.GH15145@kernel.org> (raw)
In-Reply-To: <20170224121418.GQ6515@twins.programming.kicks-ass.net>
Em Fri, Feb 24, 2017 at 01:14:18PM +0100, Peter Zijlstra escreveu:
> On Tue, Feb 21, 2017 at 07:31:23PM +0530, Hari Bathini wrote:
> > With the advert of container technologies like docker, that depend
> > on namespaces for isolation, there is a need for tracing support for
> > namespaces. This patch introduces new PERF_RECORD_NAMESPACES event
> > for recording namespaces related info. By recording info for every
> > namespace, it is left to userspace to take a call on the definition
> > of a container and trace containers by updating perf tool accordingly.
> >
> > Each namespace has a combination of device and inode numbers. Though
> > every namespace has the same device number currently, that may change
> > in future to avoid the need for a namespace of namespaces. Considering
> > such possibility, record both device and inode numbers separately for
> > each namespace.
> >
> > Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
> > ---
> > include/linux/perf_event.h | 2 +
> > include/uapi/linux/perf_event.h | 32 +++++++++
> > kernel/events/core.c | 139 +++++++++++++++++++++++++++++++++++++++
> > kernel/fork.c | 2 +
> > kernel/nsproxy.c | 3 +
> > 5 files changed, 177 insertions(+), 1 deletion(-)
>
> Arnaldo, seeing that most of this patch set is tool stuff, could you
> take the lot through the tool tree?
>
> This patch:
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Ok, looking at it now.
- Arnaldo
next prev parent reply other threads:[~2017-03-02 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:01 [PATCH v7 0/8] perf: add support for analyzing events for containers Hari Bathini
2017-02-21 14:01 ` [PATCH v7 1/8] perf: add PERF_RECORD_NAMESPACES to include namespaces related info Hari Bathini
2017-02-24 12:14 ` Peter Zijlstra
2017-03-01 20:45 ` Arnaldo Carvalho de Melo [this message]
2017-02-21 14:01 ` [PATCH v7 2/8] perf tool: " Hari Bathini
2017-03-01 21:02 ` Arnaldo Carvalho de Melo
2017-03-03 8:54 ` Hari Bathini
2017-02-21 14:01 ` [PATCH v7 3/8] perf tool: update about the new option to record namespace events Hari Bathini
2017-03-01 21:03 ` Arnaldo Carvalho de Melo
2017-02-21 14:01 ` [PATCH v7 4/8] perf tool: synthesize namespace events for current processes Hari Bathini
2017-03-01 21:05 ` Arnaldo Carvalho de Melo
2017-03-03 8:57 ` Hari Bathini
2017-02-21 14:01 ` [PATCH v7 5/8] perf tool: add print support for namespace events Hari Bathini
2017-03-01 21:06 ` Arnaldo Carvalho de Melo
2017-02-21 14:02 ` [PATCH v7 6/8] perf tool: add script " Hari Bathini
2017-03-01 21:08 ` Arnaldo Carvalho de Melo
2017-02-21 14:02 ` [PATCH v7 7/8] perf tool: update about the new option to show " Hari Bathini
2017-02-21 14:03 ` [PATCH v7 8/8] perf tool: add cgroup identifier entry in perf report Hari Bathini
2017-02-22 16:48 ` Jiri Olsa
2017-03-01 21:16 ` Arnaldo Carvalho de Melo
2017-03-03 8:59 ` Hari Bathini
2017-02-22 11:11 ` [PATCH v7 0/8] perf: add support for analyzing events for containers Jiri Olsa
2017-02-22 12:40 ` Hari Bathini
2017-02-22 13:52 ` Jiri Olsa
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=20170301204509.GH15145@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=aravinda@linux.vnet.ibm.com \
--cc=ast@fb.com \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=ebiederm@xmission.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sargun@sargun.me \
/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).