From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 3/3] perf record: Synthesize COMM event for a command line workload
Date: Wed, 20 May 2015 09:08:35 +0200 [thread overview]
Message-ID: <20150520070835.GC26714@krava.redhat.com> (raw)
In-Reply-To: <1432090115-902-3-git-send-email-namhyung@kernel.org>
On Wed, May 20, 2015 at 11:48:35AM +0900, Namhyung Kim wrote:
> When perf creates a new child to profile, the events are enabled on
> exec(). And in this case, it doesn't synthesize any event for the
> child since they'll be generated during exec(). But there's an window
> between the enabling and the event generation.
>
> It used to be overcome since samples are only in kernel (so we always
> have the map) and the comm is overridden by a later COMM event.
> However it won't work if events are processed and displayed before the
> COMM event overrides like in 'perf script'. This leads to those early
> samples (like native_write_msr_safe) not having a comm but pid (like
> ':15328').
>
> So it needs to synthesize COMM event for the child explicitly before
> enabling so that it can have a correct comm. But at this time, the
> comm will be "perf" since it's not exec-ed yet.
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/builtin-record.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 5dfe91395617..a0821ee92e27 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -469,6 +469,43 @@ static void workload_exec_failed_signal(int signo __maybe_unused,
> child_finished = 1;
> }
>
> +static int synthesize_workload_comm_event(struct perf_evlist *evlist, void *arg)
> +{
> + union perf_event *event;
> + struct record *rec = arg;
> + struct machine *machine = &rec->session->machines.host;
> + int pid = evlist->workload.pid;
> + const char *comm_str = program_invocation_short_name;
never heard of program_invocation_short_name ;-) nice..
for the patchset:
Acked-by: Jiri Olsa <jolsa@kernel.org>
I tested the record/script use case.. works ok
thanks,
jirka
prev parent reply other threads:[~2015-05-20 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 2:48 [PATCH 1/3] perf tools: Introduce perf_evlist__start_workload_ex() Namhyung Kim
2015-05-20 2:48 ` [PATCH 2/3] perf trace: Create struct thread for command line workload Namhyung Kim
2015-05-20 2:48 ` [PATCH 3/3] perf record: Synthesize COMM event for a " Namhyung Kim
2015-05-20 7:08 ` Jiri Olsa [this message]
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=20150520070835.GC26714@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.