From: Paolo Bonzini <pbonzini@redhat.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, den@virtuozzo.com,
marcandre lureau <marcandre.lureau@redhat.com>,
amit@kernel.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 03/13] char: chardevice hotswap
Date: Wed, 5 Jul 2017 17:39:59 -0400 (EDT) [thread overview]
Message-ID: <2126188994.14377452.1499290799856.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <04db742e-e15f-9743-caee-028b2f88aa0d@virtuozzo.com>
> 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
>
next prev parent reply other threads:[~2017-07-05 21:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 14:01 [Qemu-devel] [PATCH v5 00/13] chardevice hotswap Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 01/13] char: move QemuOpts->ChardevBackend translation to a separate func Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 02/13] char: add backend hotswap handler Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 03/13] char: chardevice hotswap Anton Nefedov
2017-07-05 15:09 ` Paolo Bonzini
2017-07-05 17:33 ` Anton Nefedov
2017-07-05 21:39 ` Paolo Bonzini [this message]
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 04/13] char: forbid direct chardevice access for hotswap devices Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 05/13] char: avoid chardevice direct access Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 06/13] test-char: destroy chardev-udp after test Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 07/13] test-char: split char_udp_test Anton Nefedov
2017-07-05 14:01 ` [Qemu-devel] [PATCH v5 08/13] test-char: split char_file_test Anton Nefedov
2017-07-05 14:02 ` [Qemu-devel] [PATCH v5 09/13] test-char: add hotswap test Anton Nefedov
2017-07-05 14:02 ` [Qemu-devel] [PATCH v5 10/13] hmp: add hmp analogue for qmp-chardev-change Anton Nefedov
2017-07-05 14:02 ` [Qemu-devel] [PATCH v5 11/13] virtio-console: chardev hotswap support Anton Nefedov
2017-07-05 15:12 ` Paolo Bonzini
2017-07-05 14:02 ` [Qemu-devel] [PATCH v5 12/13] serial: move TIOCM update to a separate function Anton Nefedov
2017-07-05 14:02 ` [Qemu-devel] [PATCH v5 13/13] serial: chardev hotswap support Anton Nefedov
2017-07-05 14:15 ` Michael S. Tsirkin
2017-07-05 15:12 ` Paolo Bonzini
2017-07-05 15:12 ` [Qemu-devel] [PATCH v5 00/13] chardevice hotswap Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2126188994.14377452.1499290799856.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit@kernel.org \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).