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: Mon, 15 Nov 2010 19:31:16 +0200 [thread overview]
Message-ID: <4CE16E64.2040909@redhat.com> (raw)
In-Reply-To: <1289841107.12418.602.camel@gandalf.stny.rr.com>
On 11/15/2010 07:11 PM, Steven Rostedt wrote:
> On Mon, 2010-11-15 at 19:09 +0200, Avi Kivity wrote:
> > trace-cmd doesn't like trace_printk():
> >
> > <...>-23775 [000] 26343.288803: kvm_emulate_insn: 0:f14e9: rep insb
> > <...>-23775 [000] 26343.288804: bprint: x86_emulate_insn :
> > (NO FORMAT FOUND at ffffffffa0131460)
> >
> > <...>-23775 [000] 26343.288807: bprint: x86_emulate_insn :
> > (NO FORMAT FOUND at ffffffffa0131460)
> >
> > any chance to get it to work with custom printks?
> >
> > I guess I should use 'perf probe' instead.
> >
>
> 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.
Meanwhile 'perf probe' grumbles on anonymous unions:
> src(tyep:operand) has no member val.
> Failed to find 'ctxt' in this function.
> Error: Failed to add events. (-22)
For
--add 'insb=arch/x86/kvm/emulate.c:3369 insn=ctxt->decode.b
bytes=ctxt->decode.dst.bytes port=ctxt->decode.src.val
cx=ctxt->decode.regs[1] di=ctxt->decode.regs[7]
addr=ctxt->decode.dst.mem.addr cpos=ctxt->decode.io_read.pos
cend=ctxt->decode.io_read.end'
(ctxt->decode.src.val is a member of an anonymous union in
ctxt->decode.src, which is of type 'struct operand')
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-11-15 17:31 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 [this message]
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
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=4CE16E64.2040909@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