qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 1/2] trace: document how to specify multiple --trace patterns
Date: Tue, 12 Jan 2021 16:58:58 +0000	[thread overview]
Message-ID: <20210112165859.225534-2-stefanha@redhat.com> (raw)
In-Reply-To: <20210112165859.225534-1-stefanha@redhat.com>

It is possible to repeat the --trace option to specify multiple
patterns. This may be preferrable to users who do not want to create a
file with a list of patterns.

Suggested-by: BALATON Zoltan <balaton@eik.bme.hu>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 docs/devel/tracing.rst | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/devel/tracing.rst b/docs/devel/tracing.rst
index 4ebf8e38ea..8777c19d14 100644
--- a/docs/devel/tracing.rst
+++ b/docs/devel/tracing.rst
@@ -22,10 +22,15 @@ events::
 This output comes from the "log" trace backend that is enabled by default when
 ``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified.
 
-More than one trace event pattern can be specified by providing a file
-instead::
+Multiple patterns can be specified by repeating the ``--trace`` option::
+
+    $ qemu --trace "kvm_*" --trace "virtio_*" ...
+
+When patterns are used frequently it is more convenient to store them in a
+file to avoid long command-line options::
 
     $ echo "memory_region_ops_*" >/tmp/events
+    $ echo "kvm_*" >>/tmp/events
     $ qemu --trace events=/tmp/events ...
 
 Trace events
-- 
2.29.2


  reply	other threads:[~2021-01-12 17:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 16:58 [PATCH 0/2] trace: documentation improvements Stefan Hajnoczi
2021-01-12 16:58 ` Stefan Hajnoczi [this message]
2021-01-12 18:50   ` [PATCH 1/2] trace: document how to specify multiple --trace patterns Philippe Mathieu-Daudé
2021-01-12 20:44   ` BALATON Zoltan
2021-01-13  9:48     ` Stefan Hajnoczi
     [not found]       ` <afd6945e-2666-1b80-70c8-27564cf5ac5@eik.bme.hu>
2021-01-13 14:15         ` Stefan Hajnoczi
2021-02-15 11:39           ` Kevin Wolf
2021-01-13 21:42       ` John Snow
2021-01-13 22:15         ` Eric Blake
2021-01-13 23:08           ` John Snow
2021-01-13 23:45             ` BALATON Zoltan
2021-01-14  0:20               ` John Snow
2021-01-14 14:02                 ` Stefan Hajnoczi
2021-01-14 14:18                   ` BALATON Zoltan
2021-01-14 16:44                     ` Stefan Hajnoczi
2021-01-19 16:31                     ` Eric Blake
2021-02-01 11:22                       ` Stefan Hajnoczi
2021-01-14 17:22                   ` John Snow
2021-01-12 16:58 ` [PATCH 2/2] trace: update docs with meson build information Stefan Hajnoczi
2021-02-01 11:23 ` [PATCH 0/2] trace: documentation improvements 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=20210112165859.225534-2-stefanha@redhat.com \
    --to=stefanha@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).