From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-io: add option to enable tracing
Date: Mon, 12 Mar 2012 17:54:09 +0100 [thread overview]
Message-ID: <4F5E2A31.10401@redhat.com> (raw)
In-Reply-To: <1331570167-19974-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 12.03.2012 17:36, schrieb Stefan Hajnoczi:
> It can be useful to enable QEMU tracing when trying out block layer
> interfaces via qemu-io. Tracing can be enabled using the new -T FILE
> option where the given file contains a list of trace events to enable
> (just like the qemu --trace events=FILE option).
>
> $ echo qemu_vfree >my-events
> $ ./qemu-io -T my-events ...
>
> Remember to use ./configure --enable-trace-backend=BACKEND when building
> qemu-io.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2012-03-12 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 16:36 [Qemu-devel] [PATCH v2] qemu-io: add option to enable tracing Stefan Hajnoczi
2012-03-12 16:54 ` Kevin Wolf [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=4F5E2A31.10401@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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).