From: Avi Kivity <avi@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-users@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: trace_printk() support in trace-cmd
Date: Sun, 12 Dec 2010 18:10:35 +0200 [thread overview]
Message-ID: <4D04F3FB.7060708@redhat.com> (raw)
In-Reply-To: <4CEB9CD1.8050002@redhat.com>
On 11/23/2010 12:52 PM, Avi Kivity wrote:
> On 11/16/2010 05:12 PM, Steven Rostedt wrote:
>> >
>> > 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.
>
> 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
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-12 16:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 17:09 trace_printk() support in trace-cmd Avi Kivity
2010-11-15 17:11 ` Steven Rostedt
2010-11-15 17:31 ` Avi Kivity
2010-11-15 18:33 ` Steven Rostedt
2010-11-16 9:19 ` Avi Kivity
2010-11-16 13:11 ` Steven Rostedt
2010-11-16 15:12 ` Steven Rostedt
2010-11-23 10:52 ` Avi Kivity
2010-12-12 16:10 ` Avi Kivity [this message]
2010-12-13 15:26 ` Steven Rostedt
2010-12-13 15:43 ` Avi Kivity
2010-12-13 16:28 ` Steven Rostedt
2010-12-13 17:05 ` Avi Kivity
2010-12-13 17:05 ` Avi Kivity
2010-11-16 15:13 ` Steven Rostedt
2010-11-23 11:04 ` Avi Kivity
2010-11-23 14:30 ` Steven Rostedt
2010-11-23 14:37 ` Avi Kivity
2010-11-23 15:45 ` Steven Rostedt
2010-12-12 16:35 ` Avi Kivity
2010-12-12 17:36 ` Arnaldo Carvalho de Melo
2010-12-12 17:42 ` Avi Kivity
2010-12-12 17:43 ` Arnaldo Carvalho de Melo
2010-12-12 17:47 ` Avi Kivity
2010-12-13 11:20 ` Masami Hiramatsu
2010-12-16 10:20 ` Avi Kivity
2010-12-16 13:36 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D04F3FB.7060708@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox