Skip to content

Commit 3faf22e

Browse files
committed
trace: document how to specify multiple --trace patterns
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> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Message-id: 20210112165859.225534-2-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
1 parent c6e93c9 commit 3faf22e

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

docs/devel/tracing.rst

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,15 @@ events::
2222
This output comes from the "log" trace backend that is enabled by default when
2323
``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified.
2424

25-
More than one trace event pattern can be specified by providing a file
26-
instead::
25+
Multiple patterns can be specified by repeating the ``--trace`` option::
26+
27+
$ qemu --trace "kvm_*" --trace "virtio_*" ...
28+
29+
When patterns are used frequently it is more convenient to store them in a
30+
file to avoid long command-line options::
2731

2832
$ echo "memory_region_ops_*" >/tmp/events
33+
$ echo "kvm_*" >>/tmp/events
2934
$ qemu --trace events=/tmp/events ...
3035

3136
Trace events

0 commit comments

Comments
 (0)