From: Laurent Vivier <lvivier@redhat.com>
To: Pavel Butsykin <pbutsykin@virtuozzo.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, dgilbert@redhat.com, amit@kernel.org,
pbonzini@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH] virtio-serial: add enable_backend callback
Date: Mon, 10 Jul 2017 16:13:54 +0200 [thread overview]
Message-ID: <0464adf0-801b-7083-6c3c-d8dae7ddb037@redhat.com> (raw)
In-Reply-To: <20170707142138.411-1-pbutsykin@virtuozzo.com>
On 07/07/2017 16:21, Pavel Butsykin wrote:
> We should guarantee that RAM will not be modified while VM has a stopped
> state, otherwise it can lead to negative consequences during post-copy
> migration. In RUN_STATE_FINISH_MIGRATE step, it's expected that RAM on
> source side will not be modified as this could lead to non-consistent vm state
> on the destination side. Also RAM access during postcopy-ram migration with
> enabled release-ram capability can lead to sad consequences.
>
> Let's add enable_backend() callback to avoid undesirable virtioqueue changes
> in the guest memory.
>
> Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com>
> ---
> hw/char/virtio-console.c | 21 +++++++++++++++++++++
> hw/char/virtio-serial-bus.c | 7 +++++++
> include/hw/virtio/virtio-serial.h | 3 +++
> 3 files changed, 31 insertions(+)
>
> diff --git a/hw/char/virtio-console.c b/hw/char/virtio-console.c
> index 0cb1668c8a..b55905892e 100644
> --- a/hw/char/virtio-console.c
> +++ b/hw/char/virtio-console.c
> @@ -163,6 +163,26 @@ static void chr_event(void *opaque, int event)
> }
> }
>
> +static void virtconsole_enable_backend(VirtIOSerialPort *port, bool enable)
> +{
> + VirtConsole *vcon = VIRTIO_CONSOLE(port);
> +
> + if (!qemu_chr_fe_get_driver(&vcon->chr)) {
> + return;
> + }
> +
> + if (enable) {
> + VirtIOSerialPortClass *k = VIRTIO_SERIAL_PORT_GET_CLASS(port);
> +
> + qemu_chr_fe_set_handlers(&vcon->chr, chr_can_read, chr_read,
> + k->is_console ? NULL : chr_event,
> + vcon, NULL, false);
> + } else {
> + qemu_chr_fe_set_handlers(&vcon->chr, NULL, NULL,
> + NULL, NULL, NULL, false);
> + }
> +}
I think you can also factorize the code in virtconsole_realize() to call
this new function.
> static void virtconsole_realize(DeviceState *dev, Error **errp)
> {
> VirtIOSerialPort *port = VIRTIO_SERIAL_PORT(dev);
> @@ -233,6 +253,7 @@ static void virtserialport_class_init(ObjectClass *klass, void *data)
> k->unrealize = virtconsole_unrealize;
> k->have_data = flush_buf;
> k->set_guest_connected = set_guest_connected;
> + k->enable_backend = virtconsole_enable_backend;
Why don't you register a vm_state change handler to change the state of
the virtconsole according to the state of the machine instead of adding
a new function in the VirtIOSerialPortClass?
See a23a6d1 ("virtio-rng: stop virtqueue while the CPU is stopped")
Thanks,
Laurent
next prev parent reply other threads:[~2017-07-10 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 14:21 [Qemu-devel] [PATCH] virtio-serial: add enable_backend callback Pavel Butsykin
2017-07-10 14:13 ` Laurent Vivier [this message]
2017-07-10 16:39 ` Michael S. Tsirkin
2017-07-11 9:31 ` Laurent Vivier
2017-07-10 17:23 ` Pavel Butsykin
2017-07-17 13:56 ` Pavel Butsykin
2017-09-15 9:20 ` Pavel Butsykin
2017-08-24 14:27 ` Denis V. Lunev
2017-09-15 17:09 ` Paolo Bonzini
2017-09-18 9:37 ` Pavel Butsykin
2017-09-19 7:43 ` 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=0464adf0-801b-7083-6c3c-d8dae7ddb037@redhat.com \
--to=lvivier@redhat.com \
--cc=amit@kernel.org \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pbutsykin@virtuozzo.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).