From: "KONRAD Frédéric" <fred.konrad@greensocs.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-net: require that config size is initialized
Date: Tue, 07 May 2013 14:54:38 +0200 [thread overview]
Message-ID: <5188F98E.9080203@greensocs.com> (raw)
In-Reply-To: <20130507123313.GC21361@redhat.com>
On 07/05/2013 14:33, Michael S. Tsirkin wrote:
> On Tue, May 07, 2013 at 02:29:38PM +0200, KONRAD Frédéric wrote:
>> Hi,
>>
>> I think it is not a good idea, as we wanted to make VirtIODevice
>> hot-pluggable for virtio-mmio.
> And then this hack will break cross version migration.
Why?
virtio_net_set_config_size is called by each "proxy" devices no?
>
>> Maybe we can use a callback which is called by virtio-bus before
>> plugging, to ensure that this
>> config size is computed?
> OK, will you post such a patch?
>
The issue is as we said in the last thread, host_feature is part of the
proxy.
And if we want to move it to the devices, we must have a kind of
property forwarding mechanism.
Anthony said he had something about that.
>> On 07/05/2013 12:22, Michael S. Tsirkin wrote:
>>> All buses do this, and if they don't they get subtle
>>> bugs related to cross version migration.
>>> Let's add an assert to catch these bugs early.
>>>
>>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>>> ---
>>>
>>> Just a cleanup so not 1.5 material.
>>> Seems to work fine here - any opinions?
>>>
>>> hw/net/virtio-net.c | 7 ++++---
>>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>>> index 908e7b8..f0a9272 100644
>>> --- a/hw/net/virtio-net.c
>>> +++ b/hw/net/virtio-net.c
>>> @@ -1282,6 +1282,8 @@ static int virtio_net_device_init(VirtIODevice *vdev)
>>> DeviceState *qdev = DEVICE(vdev);
>>> VirtIONet *n = VIRTIO_NET(vdev);
>>> + /* Verify that config size has been initialized */
>>> + assert(n->config_size != (size_t)-1);
>>> virtio_init(VIRTIO_DEVICE(n), "virtio-net", VIRTIO_ID_NET,
>>> n->config_size);
>>> @@ -1386,10 +1388,9 @@ static void virtio_net_instance_init(Object *obj)
>>> VirtIONet *n = VIRTIO_NET(obj);
>>> /*
>>> - * The default config_size is sizeof(struct virtio_net_config).
>>> - * Can be overriden with virtio_net_set_config_size.
>>> + * The config_size must be set later with virtio_net_set_config_size.
>>> */
>>> - n->config_size = sizeof(struct virtio_net_config);
>>> + n->config_size = (size_t)-1;
>>> }
>>> static Property virtio_net_properties[] = {
next prev parent reply other threads:[~2013-05-07 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 10:22 [Qemu-devel] [PATCH] virtio-net: require that config size is initialized Michael S. Tsirkin
2013-05-07 12:29 ` KONRAD Frédéric
2013-05-07 12:33 ` Michael S. Tsirkin
2013-05-07 12:54 ` KONRAD Frédéric [this message]
2013-05-07 14:00 ` Michael S. Tsirkin
2013-05-07 15:29 ` KONRAD Frédéric
2013-05-07 15:55 ` Michael S. Tsirkin
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=5188F98E.9080203@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).