From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Stefan Fritsch <sf@sfritsch.de>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
akong@redhat.com, qemu-devel@nongnu.org,
Anthony Liguori <aliguori@amazon.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-net: Do not filter VLANs without F_CTRL_VLAN
Date: Mon, 17 Feb 2014 07:57:38 -0700 [thread overview]
Message-ID: <53022362.4000809@redhat.com> (raw)
In-Reply-To: <20140216103305.GA28991@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
On 02/16/2014 03:33 AM, Michael S. Tsirkin wrote:
> On Wed, Feb 12, 2014 at 10:46:28PM +0100, Stefan Fritsch wrote:
>> If VIRTIO_NET_F_CTRL_VLAN is not negotiated, do not filter out all
>> VLAN-tagged packets but send them to the guest.
>>
>> Signed-off-by: Stefan Fritsch <sf@sfritsch.de>
>
> Thanks for the patch.
> I think there are still some issues after this
> patch: we need to notify management when
> this bit state changes.
> And I think libvirt still does not look at the filter info
> so it's probably not too late, and cleaner to simply tell it:
> "all-vlans".
> that is, add
> '*vlan': 'RxState',
> to the schema.
>
> (is it true that it needs to be * because old qemu does not produce it?
> maybe not ...)
The following conversions are back-compat safe:
changing an input parameter from mandatory to optional
adding an optional input parameter
changing an output parameter from optional to mandatory
adding an output parameter (optional or always-present)
Regarding whether a parameter must be marked as optional: on input,
optional means the user can omit it. On output, marking it as optional
means the current version of qemu will sometimes generate it, and
sometimes avoid it. If qemu always generates it in the current version,
even if it was not generated in an previous version, then an output
parameter does not have to be marked optional (that is, behavior of
previous qemu versions should not impact the choice of whether the
current qemu marks an output as optional - only whether the current qemu
sometimes omits the parameter). However, once an output parameter is
marked mandatory, you must never remove it in future qemu versions.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-02-17 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 21:06 [Qemu-devel] virtio-net VLAN filtering bug Stefan Fritsch
2014-02-12 21:46 ` [Qemu-devel] [PATCH] virtio-net: Do not filter VLANs without F_CTRL_VLAN Stefan Fritsch
2014-02-16 10:33 ` Michael S. Tsirkin
2014-02-17 14:57 ` Eric Blake [this message]
2014-02-17 21:31 ` Stefan Fritsch
2014-02-21 9:58 ` Amos Kong
2014-02-23 8:27 ` Stefan Fritsch
2014-02-25 3:06 ` Amos Kong
2014-03-19 22:38 ` Stefan Fritsch
2014-03-25 9:39 ` Amos Kong
2014-03-25 10:08 ` 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=53022362.4000809@redhat.com \
--to=eblake@redhat.com \
--cc=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sf@sfritsch.de \
/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).