On Mon, Mar 9, 2026 at 4:57 PM Stefan Hajnoczi <[email protected]> wrote: > > On Thu, Mar 05, 2026 at 10:24:55PM +0800, Zhang Chen wrote: > > Because of monitor create own iothread, and use the > > iothread suspend/resume with bh handler and chardev handler. > > The QOM lifecycle is hard to track. Update the legacy usage > > of "iothread_get_aio_context()" and "iothread_put_aio_context()". > > As mentioned in the prevoius patch, this feature needs to be implemented > fully in order to merged. If only half of it works, then it's not a > feature that users can rely on.
Sure, I will try to implement it as the original iothread get/put design. Hi Markus and Dave, do you have any suggestion for how to track the monitor iothread QOM lifecycle? Need to do iothread_get/put each time when monitor_suspend/resume ? Thanks Chen > > Stefan
