Vladimir Sementsov-Ogievskiy writes:
> 25.01.2022 14:03, Vladimir Sementsov-Ogievskiy wrote:
>> 25.01.2022 13:25, Markus Armbruster wrote:
>>> Vladimir Sementsov-Ogievskiy writes:
>>>
1. Add --no-trace-events to suppress trace events generation in some
cases, and make trace events
25.01.2022 14:03, Vladimir Sementsov-Ogievskiy wrote:
25.01.2022 13:25, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
1. Add --no-trace-events to suppress trace events generation in some
cases, and make trace events be generated by default.
2. Add corresponding .trace-even
25.01.2022 13:25, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
1. Add --no-trace-events to suppress trace events generation in some
cases, and make trace events be generated by default.
2. Add corresponding .trace-events files as outputs in qapi_files
custom target
3.
Vladimir Sementsov-Ogievskiy writes:
> 1. Add --no-trace-events to suppress trace events generation in some
>cases, and make trace events be generated by default.
> 2. Add corresponding .trace-events files as outputs in qapi_files
>custom target
> 3. Define global qapi_trace_events list o
On Fri, Jan 21, 2022 at 11:23 AM Vladimir Sementsov-Ogievskiy
wrote:
>
> 1. Add --no-trace-events to suppress trace events generation in some
>cases, and make trace events be generated by default.
> 2. Add corresponding .trace-events files as outputs in qapi_files
>custom target
> 3. Defin
1. Add --no-trace-events to suppress trace events generation in some
cases, and make trace events be generated by default.
2. Add corresponding .trace-events files as outputs in qapi_files
custom target
3. Define global qapi_trace_events list of .trace-events file targets,
to fill in trace