From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: ast@fb.com, peterz@infradead.org,
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 4/8] perf tool: synthesize namespace events for current processes
Date: Fri, 3 Mar 2017 14:27:09 +0530 [thread overview]
Message-ID: <f8915d66-0f21-eb43-3c82-b9f0fec4d942@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170301210558.GK15145@kernel.org>
On Thursday 02 March 2017 02:35 AM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 21, 2017 at 07:31:44PM +0530, Hari Bathini escreveu:
>> Synthesize PERF_RECORD_NAMESPACES events for processes that were
>> running prior to invocation of perf record, the data for which is
>> taken from /proc/$PID/ns. These changes make way for analyzing
>> events with regard to namespaces.
>>
>> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
>> ---
>> tools/perf/builtin-record.c | 27 +++++++++--
>> tools/perf/util/event.c | 107 +++++++++++++++++++++++++++++++++++++++++--
>> tools/perf/util/event.h | 6 ++
>> 3 files changed, 130 insertions(+), 10 deletions(-)
>>
>> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
>> index a8b9a78..f4bf6a6 100644
>> --- a/tools/perf/builtin-record.c
>> +++ b/tools/perf/builtin-record.c
>> @@ -986,6 +986,7 @@ static int __cmd_record(struct record *rec, int argc, const char **argv)
>> */
>> if (forks) {
>> union perf_event *event;
>> + pid_t tgid;
>>
>> event = malloc(sizeof(event->comm) + machine->id_hdr_size);
>> if (event == NULL) {
>> @@ -999,10 +1000,28 @@ static int __cmd_record(struct record *rec, int argc, const char **argv)
>> * cannot see a correct process name for those events.
>> * Synthesize COMM event to prevent it.
>> */
>> - perf_event__synthesize_comm(tool, event,
>> - rec->evlist->workload.pid,
>> - process_synthesized_event,
>> - machine);
>> + tgid = perf_event__synthesize_comm(tool, event,
>> + rec->evlist->workload.pid,
>> + process_synthesized_event,
>> + machine);
>> + free(event);
>> +
>> + if (tgid == -1)
>> + goto out_child;
>> +
>> + event = malloc(sizeof(event->namespaces) + machine->id_hdr_size);
>> + if (event == NULL) {
>> + err = -ENOMEM;
>> + goto out_child;
>> + }
>> +
>> + /*
>> + * Synthesize NAMESPACES event for the command specified.
>> + */
>> + perf_event__synthesize_namespaces(tool, event,
>> + rec->evlist->workload.pid,
>> + tgid, process_synthesized_event,
>> + machine);
>> free(event);
>>
>> perf_evlist__start_workload(rec->evlist);
>> diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
>> index f118eac..c8c112a 100644
>> --- a/tools/perf/util/event.c
>> +++ b/tools/perf/util/event.c
>> @@ -50,6 +50,16 @@ static const char *perf_event__names[] = {
>> [PERF_RECORD_TIME_CONV] = "TIME_CONV",
>> };
>>
>> +static const char *perf_ns__names[] = {
>> + [NET_NS_INDEX] = "net",
>> + [UTS_NS_INDEX] = "uts",
>> + [IPC_NS_INDEX] = "ipc",
>> + [PID_NS_INDEX] = "pid",
>> + [USER_NS_INDEX] = "user",
>> + [MNT_NS_INDEX] = "mnt",
>> + [CGROUP_NS_INDEX] = "cgroup",
>> +};
>> +
>> const char *perf_event__name(unsigned int id)
>> {
>> if (id >= ARRAY_SIZE(perf_event__names))
>> @@ -59,6 +69,13 @@ const char *perf_event__name(unsigned int id)
>> return perf_event__names[id];
>> }
>>
>> +static const char *perf_ns__name(unsigned int id)
>> +{
>> + if (id >= ARRAY_SIZE(perf_ns__names))
>> + return "UNKNOWN";
>> + return perf_ns__names[id];
>> +}
>> +
>> static int perf_tool__process_synth_event(struct perf_tool *tool,
>> union perf_event *event,
>> struct machine *machine,
>> @@ -204,6 +221,56 @@ pid_t perf_event__synthesize_comm(struct perf_tool *tool,
>> return tgid;
>> }
>>
>> +static void perf_event__get_ns_link_info(pid_t pid, const char *ns,
>> + struct perf_ns_link_info *ns_link_info)
>> +{
>> + struct stat64 st;
>> + char proc_ns[128];
>> +
>> + sprintf(proc_ns, "/proc/%u/ns/%s", pid, ns);
>> + if (stat64(proc_ns, &st) == 0) {
>> + ns_link_info->dev = st.st_dev;
>> + ns_link_info->ino = st.st_ino;
>> + }
>> +}
>> +
>> +int perf_event__synthesize_namespaces(struct perf_tool *tool,
>> + union perf_event *event,
>> + pid_t pid, pid_t tgid,
>> + perf_event__handler_t process,
>> + struct machine *machine)
>> +{
>> + u32 idx;
>> + struct perf_ns_link_info *ns_link_info;
>> +
>> + if (!tool->namespace_events)
>> + return 0;
>> +
>> + memset(&event->namespaces, 0,
>> + sizeof(event->namespaces) + machine->id_hdr_size);
>> +
>> + event->namespaces.pid = tgid;
>> + event->namespaces.tid = pid;
>> +
>> + event->namespaces.nr_namespaces = NR_NAMESPACES;
> Huh? Don't you have to first figure out how many namespaces a process is
> in to then set this field?
>
NR_NAMESPACES is the total number of namespaces. For synthesized namespace
events, data is obtained from /proc/<pid>/ns/ dir. Looking at this dir, it
is difficult to arrive at the total number of namespaces in kernel, as
some namespaces can be compiled in/out of the kernel. NR_NAMESPACES is
used instead. Its value is most likely the same for kernel and perf tool
unless a new namespace is introduced - the warning in previous patch is
intended to alert the user about such scenario.
Thanks
Hari
next prev parent reply other threads:[~2017-03-03 8:57 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
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 [this message]
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=f8915d66-0f21-eb43-3c82-b9f0fec4d942@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=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=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).