From: Frederic Weisbecker <fweisbec@gmail.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: simplify print_graph_cpu()
Date: Tue, 28 Jul 2009 17:53:24 +0200 [thread overview]
Message-ID: <20090728155323.GC6215@nowhere> (raw)
In-Reply-To: <4A6EEE5E.2000001@cn.fujitsu.com>
On Tue, Jul 28, 2009 at 08:26:06PM +0800, Lai Jiangshan wrote:
>
> print_graph_cpu() is little over-designed.
>
> And "log10_all" may be wrong when there are holes in cpu_online_mask:
> the max online cpu id > cpumask_weight(cpu_online_mask)
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
> index abf7c4a..e30472d 100644
> --- a/kernel/trace/trace_functions_graph.c
> +++ b/kernel/trace/trace_functions_graph.c
> @@ -183,43 +183,19 @@ static void graph_trace_reset(struct trace_array *tr)
> unregister_ftrace_graph();
> }
>
> -static inline int log10_cpu(int nb)
> -{
> - if (nb / 100)
> - return 3;
> - if (nb / 10)
> - return 2;
> - return 1;
> -}
> +static int max_bytes_for_cpu;
>
> static enum print_line_t
> print_graph_cpu(struct trace_seq *s, int cpu)
> {
> - int i;
> int ret;
> - int log10_this = log10_cpu(cpu);
> - int log10_all = log10_cpu(cpumask_weight(cpu_online_mask));
> -
>
> /*
> * Start with a space character - to make it stand out
> * to the right a bit when trace output is pasted into
> * email:
> */
> - ret = trace_seq_printf(s, " ");
> -
> - /*
> - * Tricky - we space the CPU field according to the max
> - * number of online CPUs. On a 2-cpu system it would take
> - * a maximum of 1 digit - on a 128 cpu system it would
> - * take up to 3 digits:
> - */
> - for (i = 0; i < log10_all - log10_this; i++) {
> - ret = trace_seq_printf(s, " ");
> - if (!ret)
> - return TRACE_TYPE_PARTIAL_LINE;
> - }
> - ret = trace_seq_printf(s, "%d) ", cpu);
> + ret = trace_seq_printf(s, " %*d) ", max_bytes_for_cpu, cpu);
> if (!ret)
> return TRACE_TYPE_PARTIAL_LINE;
>
> @@ -919,6 +895,8 @@ static struct tracer graph_trace __read_mostly = {
>
> static __init int init_graph_trace(void)
> {
> + max_bytes_for_cpu = snprintf(NULL, 0, "%d", nr_cpu_ids - 1);
Nice trick :-)
Queued for .32, thanks!
> +
> return register_tracer(&graph_trace);
> }
>
>
>
>
>
next prev parent reply other threads:[~2009-07-28 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 12:26 [PATCH] tracing: simplify print_graph_cpu() Lai Jiangshan
2009-07-28 15:53 ` Frederic Weisbecker [this message]
2009-08-02 19:39 ` [tip:tracing/core] tracing: Simplify print_graph_cpu() tip-bot for Lai Jiangshan
2009-08-06 12:42 ` tip-bot for Lai Jiangshan
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=20090728155323.GC6215@nowhere \
--to=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox