Vladimir Sementsov-Ogievskiy writes:
> 27.01.2022 10:32, Markus Armbruster wrote:
>> Vladimir Sementsov-Ogievskiy writes:
>>
>>> This series aims to add trace points for each qmp command with help of
>>> qapi code generator.
>> Logging QMP traffic has worked well enough for me, but I can
>> und
27.01.2022 11:21, Stefan Hajnoczi wrote:
On Wed, Jan 26, 2022 at 05:11:23PM +0100, Vladimir Sementsov-Ogievskiy wrote:
This series aims to add trace points for each qmp command with help of
qapi code generator.
v6:
01-04,07: add Stefan's r-b
01: - subject changed
- rename:
gen_trac
27.01.2022 10:32, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
This series aims to add trace points for each qmp command with help of
qapi code generator.
Logging QMP traffic has worked well enough for me, but I can understand
why you'd like to use tracing. Other uses of tr
On Wed, Jan 26, 2022 at 05:11:23PM +0100, Vladimir Sementsov-Ogievskiy wrote:
> This series aims to add trace points for each qmp command with help of
> qapi code generator.
>
> v6:
> 01-04,07: add Stefan's r-b
> 01: - subject changed
> - rename:
>gen_trace_events --> gen_tracing
>
Vladimir Sementsov-Ogievskiy writes:
> This series aims to add trace points for each qmp command with help of
> qapi code generator.
Logging QMP traffic has worked well enough for me, but I can understand
why you'd like to use tracing. Other uses of tracing might come up in
the future.
I found
This series aims to add trace points for each qmp command with help of
qapi code generator.
v6:
01-04,07: add Stefan's r-b
01: - subject changed
- rename:
gen_trace_events --> gen_tracing
_gen_trace_events --> _gen_tracing
_gent() --> _gen_trace_events()
- a bit more c