From: Jiri Olsa <jolsa@redhat.com>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@kernel.org, linux-kernel@vger.kernel.org,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 3/3] perf tools: Clarify the output of perf sched map.
Date: Mon, 5 May 2014 20:24:33 +0200 [thread overview]
Message-ID: <20140505182433.GA28367@krava.brq.redhat.com> (raw)
In-Reply-To: <a72ade72ecf55803471e42f80a3aa6547b1477e5.1399273302.git.yangds.fnst@cn.fujitsu.com>
On Mon, May 05, 2014 at 04:05:55PM +0900, Dongsheng Yang wrote:
> From: Dongsheng <yangds.fnst@cn.fujitsu.com>
>
> In output of perf sched map, any shortname of thread will be explained
> at the first time when it appear.
>
> Example:
> *A0 228836.978985 secs A0 => perf:23032
> *. A0 228836.979016 secs B0 => swapper:0
> . *C0 228836.979099 secs C0 => migration/3:22
> *A0 . C0 228836.979115 secs
> A0 . *. 228836.979115 secs
>
> But B0, which is explained as swapper:0 did not appear in the
> left part of output. Instead, we use '.' as the shortname of
> swapper:0. So the comment of "B0 => swapper:0" is not easy to
> understand.
>
> This patch clarify the output of perf sched map with not allocating
> one letter-number shortname for swapper:0 and print ". => swapper:0"
> as the explaination for swapper:0.
>
> Example:
> *A0 228836.978985 secs A0 => perf:23032
> * . A0 228836.979016 secs . => swapper:0
> . *B0 228836.979099 secs B0 => migration/3:22
> *A0 . B0 228836.979115 secs
> A0 . * . 228836.979115 secs
> A0 *C0 . 228836.979225 secs C0 => ksoftirqd/2:18
> A0 *D0 . 228836.979236 secs D0 => rcu_sched:7
I've never used 'perf sched map' before, so I'm not
sure about this one.. Arnaldo, David, Ingo? ;-)
thanks,
jirka
>
> Signed-off-by: Dongsheng <yangds.fnst@cn.fujitsu.com>
> ---
> tools/perf/builtin-sched.c | 35 +++++++++++++++++++----------------
> 1 file changed, 19 insertions(+), 16 deletions(-)
>
> diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
> index 4f0dd21..c2bf8f2 100644
> --- a/tools/perf/builtin-sched.c
> +++ b/tools/perf/builtin-sched.c
> @@ -1300,17 +1300,23 @@ static int map_switch_event(struct perf_sched *sched, struct perf_evsel *evsel,
>
> new_shortname = 0;
> if (!sched_in->shortname[0]) {
> - sched_in->shortname[0] = sched->next_shortname1;
> - sched_in->shortname[1] = sched->next_shortname2;
> -
> - if (sched->next_shortname1 < 'Z') {
> - sched->next_shortname1++;
> - } else {
> - sched->next_shortname1='A';
> - if (sched->next_shortname2 < '9') {
> - sched->next_shortname2++;
> + if (!strcmp(thread__comm_str(sched_in), "swapper")) {
> + sched_in->shortname[0] = '.';
> + sched_in->shortname[1] = '\0';
> + }
> + else {
> + sched_in->shortname[0] = sched->next_shortname1;
> + sched_in->shortname[1] = sched->next_shortname2;
> +
> + if (sched->next_shortname1 < 'Z') {
> + sched->next_shortname1++;
> } else {
> - sched->next_shortname2='0';
> + sched->next_shortname1='A';
> + if (sched->next_shortname2 < '9') {
> + sched->next_shortname2++;
> + } else {
> + sched->next_shortname2='0';
> + }
> }
> }
> new_shortname = 1;
> @@ -1322,12 +1328,9 @@ static int map_switch_event(struct perf_sched *sched, struct perf_evsel *evsel,
> else
> printf("*");
>
> - if (sched->curr_thread[cpu]) {
> - if (sched->curr_thread[cpu]->tid)
> - printf("%2s ", sched->curr_thread[cpu]->shortname);
> - else
> - printf(". ");
> - } else
> + if (sched->curr_thread[cpu])
> + printf("%2s ", sched->curr_thread[cpu]->shortname);
> + else
> printf(" ");
> }
>
> --
> 1.8.2.1
>
next prev parent reply other threads:[~2014-05-05 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:05 [PATCH 0/3] perf tools: Patchset for perf sched Dongsheng Yang
2014-05-05 7:05 ` [PATCH 1/3] perf tools: add missing event for perf sched record Dongsheng Yang
2014-05-12 16:00 ` [tip:perf/core] perf tools: Add " tip-bot for Dongsheng
2014-05-05 7:05 ` [PATCH 2/3] perf tools: Adapt the TASK_STATE_TO_CHAR_STR to new value in kernel space Dongsheng Yang
2014-05-12 16:00 ` [tip:perf/core] " tip-bot for Dongsheng
2014-05-05 7:05 ` [PATCH 3/3] perf tools: Clarify the output of perf sched map Dongsheng Yang
2014-05-05 18:24 ` Jiri Olsa [this message]
2014-05-05 18:27 ` David Ahern
2014-05-05 18:37 ` Ingo Molnar
2014-05-06 0:40 ` [PATCH V2] " Dongsheng Yang
2014-05-06 6:23 ` Ingo Molnar
2014-05-06 5:27 ` Dongsheng Yang
2014-05-06 5:39 ` [PATCH V3] " Dongsheng Yang
2014-05-06 7:23 ` Ingo Molnar
2014-05-06 12:44 ` Jiri Olsa
2014-05-12 16:01 ` [tip:perf/core] " tip-bot for Dongsheng
2014-05-05 18:25 ` [PATCH 0/3] perf tools: Patchset for perf sched 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=20140505182433.GA28367@krava.brq.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@redhat.com \
--cc=paulus@samba.org \
--cc=yangds.fnst@cn.fujitsu.com \
/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).