From: Paolo Bonzini <pbonzini@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Add a stp file for usage from build directory
Date: Tue, 28 May 2013 14:37:38 +0200 [thread overview]
Message-ID: <51A4A512.7050206@redhat.com> (raw)
In-Reply-To: <1369744385.31959.7.camel@localhost>
Il 28/05/2013 14:33, Alon Levy ha scritto:
> On Tue, 2013-05-28 at 14:18 +0200, Paolo Bonzini wrote:
>> Il 28/05/2013 14:09, Alon Levy ha scritto:
>>>>> + --probe-prefix=qemu.local \
>>>>
>>>> Why change the prefix?
>>>
>>> It was one way to verify I was using the correct file. I'll change it
>>> back.
>>>
>>> But in general does it make sense for you to have this in addition to
>>> the existing stp file?
>>
>> I think it does (with the same prefix so that you can share the
>> scripts). But I'm not sure how you'd use it. :) Can you show an
>> example and also put it in the commit message?
>
> I though it would be useful to have a bunch of scripts for developers. I
> have the following (didn't fix yet to use the same prefix):
Ok, so it's just a matter of using the -I option to stap. That's the
bit that has to be in the commit message.
Thanks!
Paolo
> diff --git a/scripts/stap-qxl-generic b/scripts/stap-qxl-generic
> new file mode 100755
> index 0000000..1c21911
> --- /dev/null
> +++ b/scripts/stap-qxl-generic
> @@ -0,0 +1,4 @@
> +#!/bin/bash -x
> +STP=$0.stp
> +ROOT=`dirname $0`/../
> +sudo stap -v -I $ROOT/x86_64-softmmu $STP
> diff --git a/scripts/stap-qxl-generic.stp b/scripts/stap-qxl-generic.stp
> new file mode 100644
> index 0000000..e201e69
> --- /dev/null
> +++ b/scripts/stap-qxl-generic.stp
> @@ -0,0 +1,24 @@
> +probe begin { printf("starting qxl generic probe\n") }
> +
> +global call, threads
> +
> +probe qemu.local.qxl* {
> + //printf("%d: %s: %s\n", tid(), pp(), $$vars)
> + //print_ubacktrace()
> + call[tid(), probefunc()] <<< 1
> + threads[tid()] <<< 1
> +}
> +
> +probe timer.s(%( $# > 0 %? $1 %: 5 %)) {
> + ansi_clear_screen()
> + printf("%10s %45s %s\n", "TID", "", "HITS");
> + foreach([t] in threads-) {
> + printf("%10d %45s %d\n", t, "", @count(threads[t]));
> + }
> + printf("%10s %45s %s\n",
> + "TID", "CALL", "HITS")
> + foreach([tid, name] in call-) {
> + printf("%10d %45s %d\n", tid, name,
> + @count(call[tid, name]))
> + }
> +}
>
>
>>
>> Paolo
>>
>>
>
>
next prev parent reply other threads:[~2013-05-28 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 2:19 [Qemu-devel] [RFC] Add a stp file for usage from build directory Alon Levy
2013-05-27 6:32 ` Paolo Bonzini
2013-05-28 12:09 ` Alon Levy
2013-05-28 12:18 ` Paolo Bonzini
2013-05-28 12:33 ` Alon Levy
2013-05-28 12:37 ` Paolo Bonzini [this message]
2013-05-28 13:25 ` Alon Levy
2013-05-28 13:57 ` Alon Levy
2013-05-28 14:17 ` Paolo Bonzini
2013-05-28 15:24 ` Stefan Hajnoczi
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=51A4A512.7050206@redhat.com \
--to=pbonzini@redhat.com \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.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.