[lkml]   [2009]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 2/5] tracing/events: nicer print format for parsing

On Tue, 9 Jun 2009, Frederic Weisbecker wrote:
> > The language that is added by this patch is of the following:
> >
> > * FMT := constant string FMT | COMMAND FMT | empty
> > * TYPE := int | hex | ptr | string | strarray
> > * FIELD := defined by the event structure
> > * MASK := the bit mask to match
> > * DELIM := delimiter to separate the fields. None and ':' are both allowed
> > * SYM := the symbol value to test against
> > * TRUE := print when field is non zero
> > * FALSE := print when field is zero or NULL
> > * NAME := the name to write when a match is found
> > *
> > * A '\<' would print '<'
> But I wonder if the above new language is not breaking the charm
> of the TRACE_EVENT(), which charm is that it's easy to implement (hopefully).
> Everyone knows the printk formats. And I guess this new thing is easy and
> quick to learn. But because it's a new unknown language, the TRACE_EVENT
> will become less readable, less reachable for newcomers in TRACE_EVENT.

I tried to avoid this too, but when I started writing a tool in C that
would parse the format file, I found that the printf was horrible.

Note, I will still keep the TP_printk() macro, that will not change. The
new macro is TP_FORMAT() that preforms the tags. Thus, if you really want
it to print out, you can use TP_printk, but the user space tools that read
the binary will not know how to read it unless the printk is simple.

I really want to keep this language simple. If anyone has any better
ideas, I'm all for it.

I barfed when I saw this in irq_handler_entry:

print fmt: "irq=%d handler=%s", REC->irq, (char *)((void *)REC + REC->__data_loc_name)

That we probably can get to show something like:

print fmt: "irq=%d handler=%s", REC->irq, __get_string(REC->name)

I plan on also adding some type tags. Perhaps adding a GFP that would do
the flags for kmem, and have a way to export the values in another file.

But for now, I would like to add the tags "major" and "minor" that would
get the major and minor from a device:

<major:dev> <minor:dev>

And also one that can handle time:

<nsec2usec:nsec> that would convert a ns time to the "%lu.%03lu" format,
or even a <nsec2sec:n:nsec> that would convert to "%lu.%0" n "lu" format.

Again, anyone have any better ideas?

-- Steve

 \ /
  Last update: 2009-06-09 21:47    [W:0.130 / U:7.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site