[v2] delay monitor iothread creation

[Qemu-devel] [PATCH v2 0/2] delay monitor iothread creation

Wolfgang Bumiller posted 2 patches 7 years, 1 month ago

Diff against v1
Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20180928075832.18586-1-w.bumiller@proxmox.com

Test checkpatch passed

Test docker-clang@ubuntu failed

monitor.c | 51 +++++++++++++++++++++++++++++++--------------------
1 file changed, 31 insertions(+), 20 deletions(-)

Expand all Fold all

[Qemu-devel] [PATCH v2 0/2] delay monitor iothread creation

Posted by Wolfgang Bumiller 7 years, 1 month ago

The early monitor iothread creation conflicts with the -daemonize option
causing crashes at shutdown of a daemonized qemu instance.
These patches will delay the creation to when a monitor using it is
actually spawned.

While the second patch depends on the first one, the first is a
consistency cleanup on its own, therefore split out.

v2:
This version incorporates Markus Armbruster's requested change to
protect mon_iothread initialization by monitor_lock (and moves the
variable declaration to reflect this), and adds a comments about
monitor_init() expecting to be run in the main thread.

Wolfgang Bumiller (2):
  monitor: guard iothread access by mon->use_io_thread
  monitor: delay monitor iothread creation

 monitor.c | 51 +++++++++++++++++++++++++++++++--------------------
 1 file changed, 31 insertions(+), 20 deletions(-)

-- 
2.11.0

Re: [Qemu-devel] [PATCH v2 0/2] delay monitor iothread creation

Posted by Peter Xu 7 years ago

On Fri, Sep 28, 2018 at 09:58:30AM +0200, Wolfgang Bumiller wrote:
> The early monitor iothread creation conflicts with the -daemonize option
> causing crashes at shutdown of a daemonized qemu instance.
> These patches will delay the creation to when a monitor using it is
> actually spawned.
> 
> While the second patch depends on the first one, the first is a
> consistency cleanup on its own, therefore split out.
> 
> v2:
> This version incorporates Markus Armbruster's requested change to
> protect mon_iothread initialization by monitor_lock (and moves the
> variable declaration to reflect this), and adds a comments about
> monitor_init() expecting to be run in the main thread.
> 
> Wolfgang Bumiller (2):
>   monitor: guard iothread access by mon->use_io_thread
>   monitor: delay monitor iothread creation

Hi, Wolfgang,

Do you have plan to repost this series?

Regards,

-- 
Peter Xu