Re: trace_printk() support in trace-cmd

[Avi Kivity <avi@redhat.com>]

On 12/13/2010 05:26 PM, Steven Rostedt wrote:
> On Sun, 2010-12-12 at 18:10 +0200, Avi Kivity wrote:
> >  On 11/23/2010 12:52 PM, Avi Kivity wrote:
>
> >  >  I see a trace_printk() commit in trace-cmd.git.  Is that related?  If
> >  >  not, I'll work on getting a small sample of the problem.
> >  >
> >
> >  Sample: http://people.redhat.com/akivity/trace.dat.bz2
> >
>
> You said previously that /debug/tracing/printk_formats was empty?

Still the case.

> This
> is the problem. It uses this file to map what the format of the printk
> is to what is being printed. But if we don't have this mapping,
> trace-cmd (nor perf) can not figure this out.
>
> You are using the latest kernel for this?

2.6.37-rc5 plus a bunch of kvm patches.

>   What's your work flow? Do you
> load kvm modules after you start the trace, or are they always loaded?

Loaded on boot.

> Are the trace_printk's in the core kernel too, and not being printed?

I don't have any trace_printk()s in the core kernel, only in modules.  
Perhaps module initialization does not communicate trace_printk formats?

-- 
error compiling committee.c: too many arguments to function