From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: allow disabling events in events file
Date: Mon, 5 Nov 2012 08:46:23 +0100 [thread overview]
Message-ID: <20121105074623.GA4616@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1351251994-12846-1-git-send-email-kraxel@redhat.com>
On Fri, Oct 26, 2012 at 01:46:34PM +0200, Gerd Hoffmann wrote:
> Disable trace events prefixed with a '-'. Useful
> to enable a group of tracepoints with exceptions,
> like this:
>
> usb_xhci_port_*
> -usb_xhci_port_read
>
> which will enable all xhci port tracepoints except reads.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> trace/control.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
Sorry for the late reply. Looks good I will send a patch to update the documentation.
Applied to the tracing tree:
http://github.com/stefanha/qemu/commits/tracing
Stefan
prev parent reply other threads:[~2012-11-05 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 11:46 [Qemu-devel] [PATCH] trace: allow disabling events in events file Gerd Hoffmann
2012-11-05 7:46 ` 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=20121105074623.GA4616@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kraxel@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).