On 1/18/22 15:22, Markus Armbruster wrote:
So, supporting auto-generated trace points for qga qmp commands requires some
deeper refactoring.
Similar trouble with tests?
The normal case seems to be "generate trace code", with an exception for
cases where our build system defeats that. Agree?
Vladimir Sementsov-Ogievskiy writes:
> 18.01.2022 13:27, Markus Armbruster wrote:
>> Vladimir Sementsov-Ogievskiy writes:
>>
>>> Add and option to generate trace events. We should generate both trace
>>> events and trace-events files for further trace events code generation.
>>
>> Can you expl
18.01.2022 13:27, Markus Armbruster wrote:
Vladimir Sementsov-Ogievskiy writes:
Add and option to generate trace events. We should generate both trace
events and trace-events files for further trace events code generation.
Can you explain why we want trace generation to be optional?
Becaus
Vladimir Sementsov-Ogievskiy writes:
> Add and option to generate trace events. We should generate both trace
> events and trace-events files for further trace events code generation.
Can you explain why we want trace generation to be optional?
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> -
Add and option to generate trace events. We should generate both trace
events and trace-events files for further trace events code generation.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
scripts/qapi/commands.py | 91 ++--
scripts/qapi/main.py | 10 +++
