summaryrefslogtreecommitdiff
path: root/trace
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2017-07-31 15:07:17 +0100
committerStefan Hajnoczi <stefanha@redhat.com>2017-08-01 12:07:48 +0100
commit3932ef3ffb54baf22ab05767e827bda1834d20df (patch)
tree69fc2ecf7b7c05e98a5677c132b34d40ef1e5503 /trace
parentea1ff54f7d2d7ac32be3c54bd171481bc2354721 (diff)
downloadqemu-3932ef3ffb54baf22ab05767e827bda1834d20df.tar.gz
trace: add TRACE_<event>_BACKEND_DSTATE()
QEMU keeps track of trace event enabled/disabled state and provides monitor commands to inspect and modify the "dstate". SystemTap and LTTng UST maintain independent enabled/disabled states for each trace event, the other backends rely on QEMU dstate. Introduce a new per-event macro that combines backend-specific dstate like this: #define TRACE_MY_EVENT_BACKEND_DSTATE() ( \ QEMU_MY_EVENT_ENABLED() || /* SystemTap */ \ tracepoint_enabled(qemu, my_event) /* LTTng UST */ || \ false) This will be used to extend trace_event_get_state() in the next patch. [Daniel Berrange pointed out that QEMU_MY_EVENT_ENABLED() must be true by default, not false. This way events will fire even if the DTrace implementation does not implement the SystemTap semaphores feature. Ubuntu Precise uses lttng-ust-dev 2.0.2 which does not have tracepoint_enabled(), so we need a compatibility wrapper to keep Travis builds passing. --Stefan] Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Message-id: 20170731140718.22010-2-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> fixup! trace: add TRACE_<event>_BACKEND_DSTATE()
Diffstat (limited to 'trace')
0 files changed, 0 insertions, 0 deletions