1QEMU-TRACE-STAP.1(1) QEMU-TRACE-STAP.1(1)
2
3
4
6 qemu-trace-stap - QEMU SystemTap trace tool
7
9 qemu-trace-stap GLOBAL-OPTIONS COMMAND COMMAND-OPTIONS ARGS...
10
12 The qemu-trace-stap program facilitates tracing of the execution of
13 QEMU emulators using SystemTap.
14
15 It is required to have the SystemTap runtime environment installed to
16 use this program, since it is a wrapper around execution of the stap
17 program.
18
20 The following global options may be used regardless of which command is
21 executed:
22
23 --verbose, -v
24 Display verbose information about command execution.
25
26 The following commands are valid:
27
28 list BINARY PATTERN...
29 List all the probe names provided by BINARY that match PATTERN.
30
31 If BINARY is not an absolute path, it will be located by searching
32 the directories listed in the $PATH environment variable.
33
34 PATTERN is a plain string that is used to filter the results of
35 this command. It may optionally contain a "*" wildcard to
36 facilitate matching multiple probes without listing each one
37 explicitly. Multiple PATTERN arguments may be given, causing
38 listing of probes that match any of the listed names. If no PATTERN
39 is given, the all possible probes will be listed.
40
41 For example, to list all probes available in the qemu-system-x86_64
42 binary:
43
44 $ qemu-trace-stap list qemu-system-x86_64
45
46 To filter the list to only cover probes related to QEMU's
47 cryptographic subsystem, in a binary outside $PATH
48
49 $ qemu-trace-stap list /opt/qemu/4.0.0/bin/qemu-system-x86_64 'qcrypto*'
50
51 run OPTIONS BINARY PATTERN...
52 Run a trace session, printing formatted output any time a process
53 that is executing BINARY triggers a probe matching PATTERN.
54
55 If BINARY is not an absolute path, it will be located by searching
56 the directories listed in the $PATH environment variable.
57
58 PATTERN is a plain string that matches a probe name shown by the
59 list command. It may optionally contain a "*" wildcard to
60 facilitate matching multiple probes without listing each one
61 explicitly. Multiple PATTERN arguments may be given, causing all
62 matching probes to be monitored. At least one PATTERN is required,
63 since stap is not capable of tracing all known QEMU probes
64 concurrently without overflowing its trace buffer.
65
66 Invocation of this command does not need to be synchronized with
67 invocation of the QEMU process(es). It will match probes on all
68 existing running processes and all future launched processes,
69 unless told to only monitor a specific process.
70
71 Valid command specific options are:
72
73 --pid=PID, -p PID
74 Restrict the tracing session so that it only triggers for the
75 process identified by "PID".
76
77 For example, to monitor all processes executing qemu-system-x86_64
78 as found on $PATH, displaying all I/O related probes:
79
80 $ qemu-trace-stap run qemu-system-x86_64 'qio*'
81
82 To monitor only the QEMU process with PID 1732
83
84 $ qemu-trace-stap run --pid=1732 qemu-system-x86_64 'qio*'
85
86 To monitor QEMU processes running an alternative binary outside of
87 $PATH, displaying verbose information about setup of the tracing
88 environment:
89
90 $ qemu-trace-stap -v run /opt/qemu/4.0.0/qemu-system-x86_64 'qio*'
91
93 qemu(1), stap(1)
94
95
96
97 2019-11-15 QEMU-TRACE-STAP.1(1)