From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 848571 <848571@bugs.launchpad.net>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 848571] [NEW] qemu does not generate a qemu-kvm.stp tapset file
Date: Tue, 13 Sep 2011 10:07:28 +0100 [thread overview]
Message-ID: <CAJSP0QWD6LB62jRHNFJxSqwCYmvq-dZFAT7eqg6d4u5PbjTDCw@mail.gmail.com> (raw)
In-Reply-To: <20110913040840.23715.80575.malonedeb@chaenomeles.canonical.com>
On Tue, Sep 13, 2011 at 5:08 AM, William Cohen
<848571@bugs.launchpad.net> wrote:
> Public bug reported:
>
> To make the systemtap probing easier to use qemu generates qemu*.stp
> files with aliases for various events for each of the executables. The
> installer places these files in /usr/share/systemtap/tapset/. These
> files are generated by the tracetool. However, the /usr/bin/qemu-kvm is
> produced with a copy:
>
> cp -a x86_64-softmmu/qemu-system-x86_64 qemu-kvm
>
> No matching qemu-kvm.stp generated for the qemu-kvm executable. It would
> be really nice if that tapset file is generated so people can use more
> symbolic probe points.
Jes Sorensen added an option to make this possible:
http://repo.or.cz/w/qemu.git/commitdiff/e323c93edf3abb67c37b8e08b78da4835880f12e
Distro packaging scripts can make use of this tracetool option to
generate .stp files for qemu-kvm in its install path.
I think you need to file a bug with your distro.
Stefan
next prev parent reply other threads:[~2011-09-13 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 4:08 [Qemu-devel] [Bug 848571] [NEW] qemu does not generate a qemu-kvm.stp tapset file William Cohen
2011-09-13 9:07 ` Stefan Hajnoczi [this message]
2011-09-13 13:35 ` [Qemu-devel] [Bug 848571] " William Cohen
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=CAJSP0QWD6LB62jRHNFJxSqwCYmvq-dZFAT7eqg6d4u5PbjTDCw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=848571@bugs.launchpad.net \
--cc=Jes.Sorensen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).