From: Thomas Gleixner
The timer flags in the timer_start trace event contain lots of useful
information, but the meaning is not clear in the trace output. Making tools
rely on the bit positions is bad as they might change over time.
Decode the flags in the print out. Tools can retrieve the bits
On Fri, 10 Feb 2017 16:41:15 +0100 (CET)
Thomas Gleixner wrote:
> The timer flags in the timer_start trace event contain lots of useful
> information, but the meaning is not clear in the trace output. Making tools
> rely on the bit positions is bad as they might change over time.
>
> Decode the
The timer flags in the timer_start trace event contain lots of useful
information, but the meaning is not clear in the trace output because its
just printed as a hex value. Making tools rely on the bit positions is bad
as they might change over time.
Decode the flags in the printout. Tools can ret
The timer flags in the timer_start trace event contain lots of useful
information, but the meaning is not clear in the trace output. Making tools
rely on the bit positions is bad as they might change over time.
Decode the flags in the print out. Tools can retrieve the bits and their
meaning from t
On Fri, 10 Feb 2017, Steven Rostedt wrote:
> On Fri, 10 Feb 2017 15:37:11 +0100 (CET)
> Thomas Gleixner wrote:
>
> > > > --- a/include/trace/events/timer.h
> > > > +++ b/include/trace/events/timer.h
> > > > @@ -36,6 +36,13 @@ DEFINE_EVENT(timer_class, timer_init,
> > > > TP_ARGS(timer)
>
On Fri, 10 Feb 2017 15:37:11 +0100 (CET)
Thomas Gleixner wrote:
> > > --- a/include/trace/events/timer.h
> > > +++ b/include/trace/events/timer.h
> > > @@ -36,6 +36,13 @@ DEFINE_EVENT(timer_class, timer_init,
> > > TP_ARGS(timer)
> > > );
> > >
> > > +#define decode_timer_flags(flags)
On Fri, 10 Feb 2017, Steven Rostedt wrote:
> On Fri, 10 Feb 2017 14:25:03 +0100 (CET)
> Thomas Gleixner wrote:
>
> > The timer flags in the timer_start trace event contain lots of useful
> > information, but the meaning is not clear in the trace output because its
> > just printed as a hex value
On Fri, 10 Feb 2017 14:25:03 +0100 (CET)
Thomas Gleixner wrote:
> The timer flags in the timer_start trace event contain lots of useful
> information, but the meaning is not clear in the trace output because its
> just printed as a hex value. Making tools rely on the bit positions is bad
> as the
8 matches
Mail list logo