On Tue, 2010-11-16 at 08:11 -0500, Steven Rostedt wrote:
> On Tue, 2010-11-16 at 11:19 +0200, Avi Kivity wrote:
> > On 11/15/2010 08:33 PM, Steven Rostedt wrote:
> > > On Mon, 2010-11-15 at 19:31 +0200, Avi Kivity wrote:
> > > > On 11/15/2010 07:11 PM, Steven Rostedt wrote:
> > >
> > > > > Which kernel are you using, and/or which trace-cmd? It works fine
> > > > for
> > > > > me. But there has been bugs with older kernels and older trace-cmds.
> > > >
> > > > kernel 2.6.37-rc1+, I think latest trace-cmd; will retry.
> > >
> > > I'm curious if you had a chance to try yet. If it is still broken I
> > > would like to fix it ASAP.
> > >
> >
> > Just did, still broken. Fixing it would be greatly appreciated.
> >
>
> Hmm, I'll try it out on the latest kernel. Would you be able to upload
> the trace.dat that does not work someplace that I can get it. I'd like
> to take a look at it. If you don't have a place to put it, I could give
> you access to my box, and you can scp it there.
Hmm, I still can not reproduce. But as a workaround, here's what you can
do for now. Instead of using trace_printk() use:
__trace_printk(_THIS_IP_, "format", args);
This will force the snprintf into the buffer and skips the bprintk trick
to post process at read time.
-- Steve
--
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
