From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alon Levy <alevy@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Add a stp file for usage from build directory
Date: Tue, 28 May 2013 17:24:51 +0200 [thread overview]
Message-ID: <20130528152451.GA17446@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1369742995.31959.1.camel@localhost>
On Tue, May 28, 2013 at 08:09:55AM -0400, Alon Levy wrote:
> On Mon, 2013-05-27 at 08:32 +0200, Paolo Bonzini wrote:
> > Il 27/05/2013 04:19, Alon Levy ha scritto:
> > > For systemtap the location of the process being tapped is crucial, so
> > > the existing stp file requires installation to use. A new file providing
> > > qemu.local prefixed probes lets scripts run without an install step.
> > >
> > > Signed-off-by: Alon Levy <alevy@redhat.com>
> > > ---
> > >
> > > Makefile.target | 13 ++++++++++++-
> > > 1 file changed, 12 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Makefile.target b/Makefile.target
> > > index ce4391f..5d176e2 100644
> > > --- a/Makefile.target
> > > +++ b/Makefile.target
> > > @@ -35,7 +35,7 @@ config-target.h: config-target.h-timestamp
> > > config-target.h-timestamp: config-target.mak
> > >
> > > ifdef CONFIG_TRACE_SYSTEMTAP
> > > -stap: $(QEMU_PROG).stp
> > > +stap: $(QEMU_PROG).stp $(QEMU_PROG).local.stp
> > >
> > > ifdef CONFIG_USER_ONLY
> > > TARGET_TYPE=user
> > > @@ -51,6 +51,17 @@ $(QEMU_PROG).stp: $(SRC_PATH)/trace-events
> > > --target-arch=$(TARGET_ARCH) \
> > > --target-type=$(TARGET_TYPE) \
> > > < $< > $@," GEN $(TARGET_DIR)$(QEMU_PROG).stp")
> > > +
> > > +$(QEMU_PROG).local.stp: $(SRC_PATH)/trace-events
> > > + $(call quiet-command,$(TRACETOOL) \
> > > + --format=stap \
> > > + --backend=$(TRACE_BACKEND) \
> > > + --binary=$(SRC_PATH)/$(TARGET_DIR)$(QEMU_PROG) \
> >
> > This is not the build directory for out-of-tree builds.
>
> I'll fix that.
>
> >
> > > + --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?
Yes, I think it makes sense.
Stefan
prev parent reply other threads:[~2013-05-28 15:25 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
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 [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=20130528152451.GA17446@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=alevy@redhat.com \
--cc=pbonzini@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).