From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Pavel Butsykin <pbutsykin@virtuozzo.com>,
qemu-devel@nongnu.org, 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 19:39:34 +0300 [thread overview]
Message-ID: <20170710193708-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0464adf0-801b-7083-6c3c-d8dae7ddb037@redhat.com>
On Mon, Jul 10, 2017 at 04:13:54PM +0200, Laurent Vivier wrote:
> > 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
In fact that commit does it the wrong way IMHO.
The order of this call wrt other virtio calls is not
guaranteed.
IMHO the right way is to set a vm state change handler in VirtioBusClass
or status change handler in VirtioDeviceClass.
--
MST
next prev parent reply other threads:[~2017-07-10 16:39 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
2017-07-10 16:39 ` Michael S. Tsirkin [this message]
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=20170710193708-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amit@kernel.org \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=lvivier@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).