From: Frederic Weisbecker <fweisbec@gmail.com>
To: mingo@kernel.org, hpa@zytor.com, paulus@samba.org,
linux-kernel@vger.kernel.org, acme@redhat.com,
a.p.zijlstra@chello.nl, namhyung.kim@lge.com,
namhyung@kernel.org, dsahern@gmail.com, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf script: Print comm, fork and exit events also
Date: Mon, 2 Dec 2013 15:35:32 +0100 [thread overview]
Message-ID: <20131202143530.GA6758@localhost.localdomain> (raw)
In-Reply-To: <tip-ad7ebb9a48f59bad2714b64725653a73d78b686e@git.kernel.org>
On Sat, Nov 30, 2013 at 04:53:07AM -0800, tip-bot for Namhyung Kim wrote:
> Commit-ID: ad7ebb9a48f59bad2714b64725653a73d78b686e
> Gitweb: http://git.kernel.org/tip/ad7ebb9a48f59bad2714b64725653a73d78b686e
> Author: Namhyung Kim <namhyung@kernel.org>
> AuthorDate: Tue, 26 Nov 2013 17:51:12 +0900
> Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
> CommitDate: Wed, 27 Nov 2013 14:58:38 -0300
>
> perf script: Print comm, fork and exit events also
>
> If --show-task-events option is given, also print internal COMM, FORK
> and EXIT events. It would be helpful for debugging.
>
> $ perf script --show-task-events
> ...
> swapper 0 [009] 3350640.335261: sched:sched_switch: prev_comm=swapper/9
> sleep 9486 [009] 3350640.335509: PERF_RECORD_COMM: sleep:9486
> sleep 9486 [009] 3350640.335806: sched:sched_stat_runtime: comm=sleep pid=9486
> firefox 2635 [003] 3350641.275896: PERF_RECORD_FORK(2635:9487):(2635:2635)
> firefox 2635 [003] 3350641.275896: sched:sched_process_fork: comm=firefox pid=2635
> sleep 9486 [009] 3350641.336009: PERF_RECORD_EXIT(9486:9486):(9486:9486)
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> Suggested-by: Frederic Weisbecker <fweisbec@gmail.com>
Thanks a lot for doing this Namhyung!
prev parent reply other threads:[~2013-12-02 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 8:51 [PATCH v3 1/2] perf script: Print comm, fork and exit events also Namhyung Kim
2013-11-26 8:51 ` [PATCH v3 2/2] perf script: Print mmap[2] " Namhyung Kim
2013-11-26 8:54 ` [PATCH v3.1 " Namhyung Kim
2013-11-30 12:53 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-11-30 12:53 ` [tip:perf/core] perf script: Print comm, fork and exit " tip-bot for Namhyung Kim
2013-12-02 14:35 ` Frederic Weisbecker [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=20131202143530.GA6758@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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