[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v5 03/13] char: chardevice hotswap
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH v5 03/13] char: chardevice hotswap |
Date: |
Wed, 5 Jul 2017 17:39:59 -0400 (EDT) |
> So instead we'll need to use proper locks in each of the front-ends?
Hi,
the only front-end actually writing from multiple threads is the monitor.
You can skip everything else, as it will be locked on the "big QEMU lock".
Paolo
> Or do you mean that it can be skipped for the most of them? I don't know
> about all possible threading cases.
> e.g. for serial/virtio-serial? Will they always share the same thread
> with hmp/qmp driven chardev-change command? And won't yield and hotswap
> in the middle of some write handler?
>
> /Anton
>
- [Qemu-devel] [PATCH v5 00/13] chardevice hotswap, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 05/13] char: avoid chardevice direct access, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 01/13] char: move QemuOpts->ChardevBackend translation to a separate func, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 04/13] char: forbid direct chardevice access for hotswap devices, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 07/13] test-char: split char_udp_test, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 02/13] char: add backend hotswap handler, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 09/13] test-char: add hotswap test, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 06/13] test-char: destroy chardev-udp after test, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 08/13] test-char: split char_file_test, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 12/13] serial: move TIOCM update to a separate function, Anton Nefedov, 2017/07/05
- [Qemu-devel] [PATCH v5 13/13] serial: chardev hotswap support, Anton Nefedov, 2017/07/05