trace: add TRACE_<event>_BACKEND_DSTATE()
commit3932ef3ffb54baf22ab05767e827bda1834d20df
authorStefan Hajnoczi <stefanha@redhat.com>
Mon, 31 Jul 2017 14:07:17 +0000 (31 15:07 +0100)
committerStefan Hajnoczi <stefanha@redhat.com>
Tue, 1 Aug 2017 11:07:48 +0000 (1 12:07 +0100)
tree69fc2ecf7b7c05e98a5677c132b34d40ef1e5503
parentea1ff54f7d2d7ac32be3c54bd171481bc2354721
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()
scripts/tracetool/__init__.py
scripts/tracetool/backend/__init__.py
scripts/tracetool/backend/dtrace.py
scripts/tracetool/backend/ftrace.py
scripts/tracetool/backend/log.py
scripts/tracetool/backend/simple.py
scripts/tracetool/backend/syslog.py
scripts/tracetool/backend/ust.py
scripts/tracetool/format/h.py