From: Avi Kivity <avi@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: kernelshark plugins and ftrace array fields
Date: Thu, 02 Sep 2010 15:19:05 +0300 [thread overview]
Message-ID: <4C7F9639.7000804@redhat.com> (raw)
I'd like to add enhance kvm_emulate_insn display in kernelshark to
show the disassembly of the instruction being emulated. However,
pevent_get_field_val() doesn't support arrays (the instruction is
provided in a 15-byte array).
Can you add support for arrays in the kernelshark API? With that, it
looks like adding disassembly output to the kvm plugin should be quite
simple.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2010-09-02 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 12:19 Avi Kivity [this message]
2010-09-02 14:25 ` kernelshark plugins and ftrace array fields Steven Rostedt
2010-09-02 14:34 ` Avi Kivity
2010-09-02 15:52 ` Steven Rostedt
2010-09-02 16:06 ` Avi Kivity
2010-09-02 17:55 ` Steven Rostedt
2010-09-02 18:16 ` Steven Rostedt
2010-09-02 18:38 ` Steven Rostedt
2010-09-02 19:24 ` Steven Rostedt
2010-09-05 7:08 ` Avi Kivity
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=4C7F9639.7000804@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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