On Wed, Jan 11, 2023 at 12:45:06PM +0800, Jason Wang wrote:
> On Wed, Jan 11, 2023 at 11:23 AM Heng Qi <[email protected]> wrote:
> >
> >
> >
> > 在 2023/1/10 下午3:26, Heng Qi 写道:
> > > On Tue, Jan 10, 2023 at 12:57:38AM -0500, Michael S. Tsirkin wrote:
> > >> On Tue, Jan 10, 2023 at 12:25:02AM -0500, Michael S. Tsirkin wrote:
> > >>>> This will give extra pressure on the management stack, e.g it requires
> > >>>> the device to have an out of spec way for introspection.
> > >>>>
> > >>>> Thanks
> > >>> As I tried to explain this is already the case. Feature bits do not
> > >>> describe device capabilities fully, some of them are in config space.
>
> Yes.
>
> > >> To be precise, this does not necessarily require introspection, but
> > >> it does require management control over config space
> > >> such as supported hash types just like it has control over feature bits.
> > >> E.g. QEMU currently seems to hard-code these to
> > >> #define VIRTIO_NET_RSS_SUPPORTED_HASHES (VIRTIO_NET_RSS_HASH_TYPE_IPv4 |
> > >> \
> > >> VIRTIO_NET_RSS_HASH_TYPE_TCPv4
> > >> | \
> > >> VIRTIO_NET_RSS_HASH_TYPE_UDPv4
> > >> | \
> > >> VIRTIO_NET_RSS_HASH_TYPE_IPv6
> > >> | \
> > >> VIRTIO_NET_RSS_HASH_TYPE_TCPv6
> > >> | \
> > >> VIRTIO_NET_RSS_HASH_TYPE_UDPv6
> > >> | \
> > >> VIRTIO_NET_RSS_HASH_TYPE_IP_EX
> > >> | \
> > >>
> > >> VIRTIO_NET_RSS_HASH_TYPE_TCP_EX | \
> > >>
> > >> VIRTIO_NET_RSS_HASH_TYPE_UDP_EX)
> > >>
> > >> but there's no reason not to give management control over these.
>
> Note that the management expects the migration compatibility to work
> with machine types. So it needs a way to disable some tunnel hash
> types to make it work for old machine types.
yes.
This means qemu will need to create properties for these things
and control through machine type compatibility machinery.
For those not hacking qemu - "machine type" is
a string roughly describing a version of guest/host interface used.
> > > Yes, QEMU has requirements for live migration: the PCI config space will
> > > be
> > > checked in get_pci_config_device(), and if src and dst are inconsistent,
> > > it
> > > will prompt that the live migration failed.
>
> It might be too late since it can't work for the second run (unlike
> subsection).
This is really a low level detail of qemu. I'm not sure how important
this is for the spec.
> >
> > To be clearer, I mean \filed{supported_hash_types} in structure
> > virtio_net_config.
>
> Yes.
>
> Thanks
>
> >
> > Thanks.
> >
> > > In fact, this is also done within our group. Live migration requires that
> > > the two VMs have the same rss configuration, otherwise the migration will
> > > fail.
> > >
> > > Therefore, it seems that we can regularize the description of
> > > VIRTIO_NET_F_HASH_TUNNEL into
> > > "[VIRTIO_NET_F_HASH_TUNNEL(52)] Device supports inner header hash for
> > > tunnel-encapsulated packets.",
> > > and use different hash_types to help the migration determine whether it
> > > can succeed.
> > >
> > > Thanks.
> > >
> > >> --
> > >> MST
> > > This publicly archived list offers a means to provide input to the
> > > OASIS Virtual I/O Device (VIRTIO) TC.
> > >
> > > In order to verify user consent to the Feedback License terms and
> > > to minimize spam in the list archive, subscription is required
> > > before posting.
> > >
> > > Subscribe: [email protected]
> > > Unsubscribe: [email protected]
> > > List help: [email protected]
> > > List archive: https://lists.oasis-open.org/archives/virtio-comment/
> > > Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> > > List Guidelines:
> > > https://www.oasis-open.org/policies-guidelines/mailing-lists
> > > Committee: https://www.oasis-open.org/committees/virtio/
> > > Join OASIS: https://www.oasis-open.org/join/
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
