[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140506072304.GA25402@gmail.com>
Date: Tue, 6 May 2014 09:23:04 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Dongsheng Yang <yangds.fnst@...fujitsu.com>
Cc: jolsa@...hat.com, a.p.zijlstra@...llo.nl, paulus@...ba.org,
acme@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3] perf tools: Clarify the output of perf sched map.
* Dongsheng Yang <yangds.fnst@...fujitsu.com> wrote:
> From: Dongsheng <yangds.fnst@...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
>
> Signed-off-by: Dongsheng <yangds.fnst@...fujitsu.com>
> Acked-by: Ingo Molnar <mingo@...nel.org>
Looks good to me, thanks!
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists