All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-trace-users@vger.kernel.org
Cc: KVM list <kvm@vger.kernel.org>
Subject: trace_printk() support in trace-cmd
Date: Mon, 15 Nov 2010 19:09:21 +0200	[thread overview]
Message-ID: <4CE16941.3080008@redhat.com> (raw)

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.

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


             reply	other threads:[~2010-11-15 17:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 17:09 Avi Kivity [this message]
2010-11-15 17:11 ` trace_printk() support in trace-cmd 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
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=4CE16941.3080008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.