From: "Denis V. Lunev" <den@openvz.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] trace: enable tracing in qemu-io/qemu-nbd
Date: Tue, 31 May 2016 12:26:49 +0300 [thread overview]
Message-ID: <574D58D9.4060002@openvz.org> (raw)
In-Reply-To: <20160531092530.GK21628@redhat.com>
On 05/31/2016 12:25 PM, Daniel P. Berrange wrote:
> On Tue, May 31, 2016 at 11:58:14AM +0300, Denis V. Lunev wrote:
>> Actually this is a rework of the original patch, set as a part of write-zeroes
>> patchset. Moving it out to process via trace tree.
>>
>> Changes from v1:
>> - fixed nits found by Eric
>>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Eric Blake <eblake@redhat.com>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>> CC: Stefan Hajnoczi <stefanha@redhat.com>
>> CC: Kevin Wolf <kwolf@redhat.com>
>>
>> Denis V. Lunev (3):
>> trace: move qemu_trace_opts to trace/control.c
>> trace: enable tracing in qemu-io
>> trace: enable tracing in qemu-nbd
> Cool, I wanted this feature just the other day ! Do you fancy
> also addinbg it to qemu-img while you're at it, so we have
> complete coverage of all block tools.
>
>
> Regards,
> Daniel
ok. no prob ;)
prev parent reply other threads:[~2016-05-31 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:58 [Qemu-devel] [PATCH v2 0/3] trace: enable tracing in qemu-io/qemu-nbd Denis V. Lunev
2016-05-31 8:58 ` [Qemu-devel] [PATCH 1/3] trace: move qemu_trace_opts to trace/control.c Denis V. Lunev
2016-05-31 8:58 ` [Qemu-devel] [PATCH 2/3] trace: enable tracing in qemu-io Denis V. Lunev
2016-05-31 17:55 ` Eric Blake
2016-05-31 8:58 ` [Qemu-devel] [PATCH 3/3] trace: enable tracing in qemu-nbd Denis V. Lunev
2016-05-31 12:46 ` Eric Blake
2016-05-31 9:25 ` [Qemu-devel] [PATCH v2 0/3] trace: enable tracing in qemu-io/qemu-nbd Daniel P. Berrange
2016-05-31 9:26 ` Denis V. Lunev [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=574D58D9.4060002@openvz.org \
--to=den@openvz.org \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.