Re: [Qemu-devel] [PATCH v2 1/2] trace: add TRACE__BACKEND_DSTATE()

2017-08-01 Thread Daniel P. Berrange
On Mon, Jul 31, 2017 at 05:35:11PM +0100, Stefan Hajnoczi wrote: > On Mon, Jul 31, 2017 at 04:16:39PM +0100, Daniel P. Berrange wrote: > > On Mon, Jul 31, 2017 at 03:07:17PM +0100, Stefan Hajnoczi wrote: > > > diff --git a/scripts/tracetool/backend/dtrace.py > > >

Re: [Qemu-devel] [PATCH v2 1/2] trace: add TRACE__BACKEND_DSTATE()

2017-07-31 Thread Stefan Hajnoczi
On Mon, Jul 31, 2017 at 04:16:39PM +0100, Daniel P. Berrange wrote: > On Mon, Jul 31, 2017 at 03:07:17PM +0100, Stefan Hajnoczi wrote: > > diff --git a/scripts/tracetool/backend/dtrace.py > > b/scripts/tracetool/backend/dtrace.py > > index c6812b70a2..17f902cc62 100644 > > ---

Re: [Qemu-devel] [PATCH v2 1/2] trace: add TRACE__BACKEND_DSTATE()

2017-07-31 Thread Daniel P. Berrange
On Mon, Jul 31, 2017 at 03:07:17PM +0100, Stefan Hajnoczi wrote: > 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

[Qemu-devel] [PATCH v2 1/2] trace: add TRACE__BACKEND_DSTATE()

2017-07-31 Thread Stefan Hajnoczi
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