On 11/23/2010 04:30 PM, Steven Rostedt wrote:
On Tue, 2010-11-23 at 13:04 +0200, Avi Kivity wrote:
> On 11/16/2010 05:13 PM, Steven Rostedt wrote:
> > BTW, what does /debug/tracing/printk_formats show?
> >
>
> Empty.
>
So you have real trace_printk's not bprintk's?
What are bprintk()s?
That is, if the format is not a const, then we fall back to
__trace_printk(_THIS_IP_, fmt, args);
And this is a different object. I have not tested these in a while, I'll
give it a try.
But if your printks are bprintks, then the bug is in the kernel, since
that printk_formats needs to show something.
What I do is sprinkle trace_printk()s around my code and expect to see
them interspersed with enabled tracepoints in 'trace-cmd report'. Is
that not the intended behaviour?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
