Re: [PATCH] tracing: branch tracer, tweak output

From: Ingo Molnar
Date: Wed Nov 12 2008 - 08:15:07 EST



* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

>
> On Wed, 12 Nov 2008, Ingo Molnar wrote:
>
> >
> > a small detail:
> >
> > > For example:
> > >
> > > bash-3471 [003] 357.014755: [INCORRECT] sched_info_dequeued:sched_stats.h:177
> > > bash-3471 [003] 357.014756: [correct] update_curr:sched_fair.c:489
> > > bash-3471 [003] 357.014758: [correct] calc_delta_fair:sched_fair.c:411
> > > bash-3471 [003] 357.014759: [correct] account_group_exec_runtime:sched_stats.h:356
> > > bash-3471 [003] 357.014761: [correct] update_curr:sched_fair.c:489
> > > bash-3471 [003] 357.014763: [INCORRECT] calc_delta_fair:sched_fair.c:411
> > > bash-3471 [003] 357.014765: [correct] calc_delta_mine:sched.c:1279
> >
> > it's always good to have such fields aligned vertically. Something
> > like this would be shorter and visually much easier to parse:
> >
> > bash-3471 [003] 357.014755: [ MISS ] sched_info_dequeued:sched_stats.h:177
> > bash-3471 [003] 357.014756: [ .... ] update_curr:sched_fair.c:489
> > bash-3471 [003] 357.014758: [ .... ] calc_delta_fair:sched_fair.c:411
> >
> > any objections against the patch below which implements this?
>
> How about "[ OK ]" instead of "[ .... ]". That would be easier to
> understand.

ok, agreed - just the use of capitals is not good, as it unnecessarily
draws visual attention. How about:

> bash-3471 [003] 357.014755: [ MISS ] sched_info_dequeued:sched_stats.h:177
> bash-3471 [003] 357.014756: [ ok ] update_curr:sched_fair.c:489
> bash-3471 [003] 357.014758: [ ok ] calc_delta_fair:sched_fair.c:411

via the patch below?

Ingo

-------------->