qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability
Date: Wed, 17 Nov 2010 11:36:48 +0000	[thread overview]
Message-ID: <20101117113648.GB29020@redhat.com> (raw)
In-Reply-To: <AANLkTik6xjnE0hmwVX5JB5hrO8ex1xXp6b-bQXMz0dmy@mail.gmail.com>

On Tue, Nov 16, 2010 at 06:54:57PM +0000, Peter Maydell wrote:
> On 16 November 2010 18:10, Anthony Liguori <anthony@codemonkey.ws> wrote:
> > On 11/16/2010 11:43 AM, Peter Maydell wrote:
> >> Unfortunately these commits:
> >> 2834c3e Add support for generating a systemtap tapset static probes
> >> 4addb11 Add a DTrace tracing backend targetted for SystemTAP compatability
> >
> > What's your configure output?
> 
> I've attached it; the trace related bits are:
> Trace backend     nop
> Trace output file trace-<pid>
> 
> > I don't have the right environment to build with systemtap support, but
> > --trace-backend=nop should work regardless.
> 
> I'm using the nop backend, yes.
> 
> I think the problem is that commit 2834c3e adds a target 'trace:' to the
> Makefile.target which looks like it's intended to be a phony target. However
> it isn't marked as such, so make actually tries to create a binary 'trace'
> by falling back to its default rules (since there's a "trace.c" in the root
> directory):

This Makefile problem was fixed in the v6 patches I posted on Nov 12th

http://lists.gnu.org/archive/html/qemu-devel/2010-11/msg01033.html

Unfortunately the v5 patches were applied by mistake.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  parent reply	other threads:[~2010-11-17 11:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 19:33 [Qemu-devel] [PATCH 0/2] Add support for SystemTAP and DTrace tracing backends (v5) Daniel P. Berrange
2010-11-08 19:33 ` [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability Daniel P. Berrange
2010-11-16 15:46   ` Anthony Liguori
2010-11-16 17:43     ` Peter Maydell
2010-11-16 18:10       ` Anthony Liguori
2010-11-16 18:54         ` Peter Maydell
2010-11-16 18:58           ` Anthony Liguori
2010-11-16 20:07             ` [Qemu-devel] [PATCH] Fix compilation failure with simple trace when srcdir==objdir Peter Maydell
2010-11-16 21:12               ` Stefan Hajnoczi
2010-11-16 22:25               ` Anthony Liguori
2010-11-16 20:22             ` [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability Peter Maydell
2010-11-17 11:36           ` Daniel P. Berrange [this message]
2010-11-17 11:35     ` Daniel P. Berrange
2010-11-18  0:00       ` Anthony Liguori
2010-11-18 15:58         ` Stefan Hajnoczi
2010-11-08 19:33 ` [Qemu-devel] [PATCH 2/2] Add support for generating a systemtap tapset static probes Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2010-11-12 13:20 [Qemu-devel] Add support for SystemTAP and DTrace tracing backends (v6) Daniel P. Berrange
2010-11-12 13:20 ` [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability Daniel P. Berrange
2010-11-12 13:30   ` Stefan Hajnoczi
2010-11-08 11:33 [Qemu-devel] [PATCH 0/2] Add support for SystemTAP and DTrace tracing backends Daniel P. Berrange
2010-11-08 11:33 ` [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability Daniel P. Berrange
2010-11-08 16:52   ` Stefan Hajnoczi
2010-11-08 16:57     ` Daniel P. Berrange
2010-11-08 19:29       ` 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=20101117113648.GB29020@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).