Home
last modified time | relevance | path

Searched refs:trace (Results 1 – 25 of 52) sorted by relevance

123

/qemu/docs/devel/
H A Dtracing.rst19 $ qemu --trace "memory_region_ops_*" ...
24 This output comes from the "log" trace backend that is enabled by default when
25 ``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified.
27 Multiple patterns can be specified by repeating the ``--trace`` option::
29 $ qemu --trace "kvm_*" --trace "virtio_*" ...
36 $ qemu --trace events=/tmp/events ...
44 Each directory in the source tree can declare a set of trace events in a local
45 "trace-events" file. All directories which contain "trace-events" files must be
47 file. During build, the "trace-events" file in each listed subdirectory will be
48 processed by the "tracetool" script to generate code for the trace events.
[all …]
/qemu/scripts/oss-fuzz/
H A Dreorder_fuzzer_qtest_trace.py81 trace = f.readlines()
84 trace[:] = [x.strip() for x in trace if "[R +" in x
87 for i in range(len(trace)):
88 if i+1 < len(trace):
89 if "[DMA]" in trace[i+1]:
90 if "[DOUBLE-FETCH]" in trace[i+1]:
95 trace[i], trace[i+1] = trace[i+1], trace[i]
96 for line in trace:
H A Doutput_reproducer.py52 def bash_reproducer(path, args, trace): argument
56 for l in trace.splitlines():
61 def c_reproducer(name, args, trace): argument
71 for l in trace.splitlines():
143 trace = args.input_trace.read().strip()
146 print(bash_reproducer(qemu_path, bash_args, trace))
152 output += c_comment(bash_reproducer(qemu_path, bash_args, trace))
153 output += c_reproducer(args.name, qemu_args, trace)
H A Dminimize_qtest_trace.py53 def check_if_trace_crashes(trace, path): argument
55 tracefile.write("".join(trace))
279 trace = f.readlines()
281 if not check_if_trace_crashes(trace, outpath):
288 newtrace = trace[:]
/qemu/trace/
H A Dmeson.build1 system_ss.add(files('control-target.c', 'trace-hmp-cmds.c'))
9 trace_events_file = meson.project_source_root() / item / 'trace-events'
16 trace_h = custom_target(fmt.format('trace', 'h'),
17 output: fmt.format('trace', 'h'),
22 trace_c = custom_target(fmt.format('trace', 'c'),
23 output: fmt.format('trace', 'c'),
28 trace_ust_h = custom_target(fmt.format('trace-ust', 'h'),
29 output: fmt.format('trace-ust', 'h'),
38 trace_dtrace = custom_target(fmt.format('trace-dtrace', 'dtrace'),
39 output: fmt.format('trace-dtrace', 'dtrace'),
[all …]
/qemu/docs/tools/
H A Dqemu-trace-stap.rst2 QEMU SystemTap trace tool
8 **qemu-trace-stap** [*GLOBAL-OPTIONS*] *COMMAND* [*COMMAND-OPTIONS*] *ARGS*...
13 The ``qemu-trace-stap`` program facilitates tracing of the execution
23 .. program:: qemu-trace-stap
54 $ qemu-trace-stap list |qemu_system|
61 $ qemu-trace-stap list /opt/qemu/|version|/bin/|qemu_system| 'qcrypto*'
65 Run a trace session, printing formatted output any time a process that is
77 its trace buffer.
86 .. program:: qemu-trace-stap-run
98 $ qemu-trace-stap run |qemu_system| 'qio*'
[all …]
H A Dindex.rst17 qemu-trace-stap
H A Dqemu-pr-helper.rst73 .. option:: -T, --trace [[enable=]PATTERN][,events=FILE][,file=FILE]
75 .. include:: ../qemu-option-trace.rst.inc
H A Dqemu-vmsr-helper.rst71 .. option:: -T, --trace [[enable=]PATTERN][,events=FILE][,file=FILE]
73 .. include:: ../qemu-option-trace.rst.inc
/qemu/
H A Dtrace-events5 # To add a new trace event:
7 # 1. Choose a name for the trace event. Declare its arguments and format
10 # 2. Call the trace event from code using trace_##name, e.g. multiwrite_cb() ->
11 # trace_multiwrite_cb(). The source file must #include "trace.h".
13 # Format of a trace event:
19 # The "disable" keyword will build without the trace event.
23 # Types should be standard C types. Use void * for pointers because the trace
H A Dhmp-commands-info.hx582 .name = "trace-events",
585 .help = "show available trace-events & their state "
592 ``info trace-events``
593 Show available trace-events & their state.
/qemu/docs/
H A Dqemu-option-trace.rst.inc10 specify the :option:`-trace` option multiple times.
12 Use :option:`-trace help` to print a list of names of trace points.
17 The file must contain one event name (as listed in the ``trace-events-all``
/qemu/qapi/
H A Dtrace.json44 # @trace-event-get-state:
60 { 'command': 'trace-event-get-state',
65 # @trace-event-set-state:
83 { 'command': 'trace-event-set-state',
H A Dmeson.build52 'trace',
108 'qapi-commands-@0@.trace-events'.format(module),
125 if output.endswith('.trace-events')
H A Dqapi-schema.json52 { 'include': 'trace.json' }
/qemu/tests/
H A Dmeson.build35 # Problem: to generate trace events, we'd have to add the .trace-events
37 # qapi_trace_events is used by trace/meson.build, we'd have to move
38 # subdir('tests') above subdir('trace') in the top-level meson.build.
40 # depends on trace_ss). Not worth solving now; simply suppress trace
/qemu/qga/
H A Dmeson.build48 # Problem: to generate trace events, we'd have to add the .trace-events
50 # qapi_trace_events is used by trace/meson.build, we'd have to move
51 # subdir('qga') above subdir('trace') in the top-level meson.build.
53 # depends on trace_ss). Not worth solving now; simply suppress trace
/qemu/scripts/
H A Danalyze-inclusions91 echo trace/generated-tracers.h:
92 analyze -include ../include/qemu/osdep.h trace/generated-tracers.h
H A Dmeson.build2 install_data('qemu-trace-stap', install_dir: get_option('bindir'))
/qemu/docs/system/devices/
H A Dcanokey.rst35 * CanoKey QEMU supports trace event thus event
113 If you want to trace what happens inside the secure key, when compiling
121 If you want to trace events happened in canokey.c, use
125 |qemu_system| --trace "canokey_*" \\
/qemu/tests/docker/
H A Dtest-mingw22 --enable-trace-backends=simple \
/qemu/target/ppc/
H A Dtrace-events16 kvm_failed_dtl_get(const char *msg) "Unable to get dispatch trace log state from KVM: %s"
19 kvm_failed_dtl_set(const char *msg) "Unable to set dispatch trace log state to KVM: %s"
/qemu/scripts/coverity-scan/
H A DCOMPONENTS.md114 trace
115 ~ .*/qemu(/.*trace.*\.[ch])
/qemu/hw/remote/
H A Dtrace-events1 # multi-process trace events
/qemu/docs/devel/testing/
H A Dfuzzing.rst225 qemu-fuzz-i386 --fuzz-target... ./crash-... &> /tmp/trace
227 - Reorder and clean-up the resulting trace::
229 scripts/oss-fuzz/reorder_fuzzer_qtest_trace.py /tmp/trace > /tmp/reproducer
233 less /tmp/trace # The args should be logged at the top of this file
242 can be a line in the stack-trace, for example::

123