Re: [PATCH 0/5] trace: inroduce qmp: trace namespace

2021-10-26 Thread Markus Armbruster
Stefan Hajnoczi writes: > On Thu, Oct 14, 2021 at 06:22:32PM +0300, Vladimir Sementsov-Ogievskiy wrote: >> 12.10.2021 14:49, Markus Armbruster wrote: >> > Vladimir Sementsov-Ogievskiy writes: [...] >> Another possible way is to update QAPI code generator to insert a personal >> trace point

Re: [PATCH 0/5] trace: inroduce qmp: trace namespace

2021-10-25 Thread Stefan Hajnoczi
On Thu, Oct 14, 2021 at 06:22:32PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 12.10.2021 14:49, Markus Armbruster wrote: > > Vladimir Sementsov-Ogievskiy writes: > > > > > Hi all! > > > > > > We have handle_qmp_command and qmp_command_repond trace points to trace > > > qmp commands. They are

Re: [PATCH 0/5] trace: inroduce qmp: trace namespace

2021-10-14 Thread Vladimir Sementsov-Ogievskiy
12.10.2021 14:49, Markus Armbruster wrote: Vladimir Sementsov-Ogievskiy writes: Hi all! We have handle_qmp_command and qmp_command_repond trace points to trace qmp commands. They are very useful to debug problems involving management tools like libvirt. But tracing all qmp commands is too

Re: [PATCH 0/5] trace: inroduce qmp: trace namespace

2021-10-12 Thread Markus Armbruster
Vladimir Sementsov-Ogievskiy writes: > Hi all! > > We have handle_qmp_command and qmp_command_repond trace points to trace > qmp commands. They are very useful to debug problems involving > management tools like libvirt. > > But tracing all qmp commands is too much. > > Here I suggest a kind of