public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Re: kernelshark plugins and ftrace array fields
Date: Sun, 05 Sep 2010 10:08:17 +0300	[thread overview]
Message-ID: <4C8341E1.7050605@redhat.com> (raw)
In-Reply-To: <1283455443.2356.433.camel@gandalf.stny.rr.com>

  On 09/02/2010 10:24 PM, Steven Rostedt wrote:
>
> I just pushed out the changes and my new example looks like this:
>
> static int
> kvm_emulate_insn_handler(struct trace_seq *s, struct record *record,
>                           struct event_format *event, void *context)
> {
>          unsigned char *data;
>          int len;
>          int i;
>
>          data = pevent_get_field_raw(s, event, "insn", record,
>                                      &len, 1);
>          if (!data)
>                  return -1;
>
>          trace_seq_puts(s, "insn: ");
>          for (i = 0; i<  len; i++) {
>                  trace_seq_printf(s, "%s%02x",
>                                   i ? "," : "",
>                                   data[i]);
>          }
>
>          return 0;
> }
>

That looks perfect.  But on which branch can I find it?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


      reply	other threads:[~2010-09-05  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 12:19 kernelshark plugins and ftrace array fields Avi Kivity
2010-09-02 14:25 ` 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 [this message]

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=4C8341E1.7050605@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