From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] Add a DTrace tracing backend targetted for SystemTAP compatability
Date: Thu, 18 Nov 2010 15:58:31 +0000 [thread overview]
Message-ID: <AANLkTimxSPBNHF7bxuqVMfhVAFWCy5nCDdW5tjg9q_9A@mail.gmail.com> (raw)
In-Reply-To: <4CE46CAD.5070109@codemonkey.ws>
On Thu, Nov 18, 2010 at 12:00 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>> Applied both. Thanks.
>>>
>>
>> I'm afraid you have applied an old version of the patches. Please
>> revert these, and apply version 6, from Nov 12th
>>
>
> Sure, sorry about that.
>
> But in the future, please indicate the version somewhere in the patch
> (preferrably the header).
Here's the changelog from v5 to v6:
- Fix handling of probes with no-args in DTrace provider
- Generate one tapset per target, for both system and user
emulators
- Re-write command line arg parsing in tracetool so it
doesn't assume a particular ordering of args
- Change '-s' to '--stap' in tracetool to avoid confusion
- Pass full binary name into tracetool
It would be nice to have v6. Is it possible to revert v5 and apply v6 instead?
Stefan
next prev parent reply other threads:[~2010-11-18 15:58 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
2010-11-17 11:35 ` Daniel P. Berrange
2010-11-18 0:00 ` Anthony Liguori
2010-11-18 15:58 ` Stefan Hajnoczi [this message]
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=AANLkTimxSPBNHF7bxuqVMfhVAFWCy5nCDdW5tjg9q_9A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=prerna@linux.vnet.ibm.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).