qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Xu <peterx@redhat.com>,
	eduardo@habkost.net, marcel.apfelbaum@gmail.com,
	 philmd@linaro.org, wangyanan55@huawei.com, zhao1.liu@intel.com,
	 qemu-devel@nongnu.org, farosas@suse.de, jinpu.wang@ionos.com,
	 thuth@redhat.com, berrange@redhat.com
Subject: Re: [RFC PATCH] virtio-net: introduce strict peer feature check
Date: Thu, 20 Nov 2025 09:45:24 +0800	[thread overview]
Message-ID: <CACGkMEusFr2Ge0GthiEkhwkZ6ncByrVFkL6BcTrHmCK4TmEiOA@mail.gmail.com> (raw)
In-Reply-To: <20251119030622-mutt-send-email-mst@kernel.org>

On Wed, Nov 19, 2025 at 4:07 PM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Wed, Nov 19, 2025 at 10:49:11AM +0800, Jason Wang wrote:
> > > qemu already probes tap features.
> >
> > Only part of the features.
>
>
> the part we care about?

Yes and technically Qemu can probe all.

>
> > > To me, it seems natural
> > > for management to do the probing through qemu.
> > > in fact your patch is a way to do that, is it not?
> >
> > Yes and no.
> >
> > > what it lacks though is a structured way to tell management how
> > > to fix the problem.
> >
> > Probing through management seems to be better. For example it can
> > calculate the cluster in advance without the need to launch qemu
> > everywhere.
>
> it is basically replicating qemu code then.

Yes but libvirt has duplicated somehow, e.g create and destroy TAP and
it even uses TUNGETFEATURES in virNetDevMacVLanTapSetup(). But I'm not
even sure this is the work of the libvirt. I think it should be the
job of the one who is in charge of managing the cpu cluster.

>
> what's the big deal to launch qemu?

It looks more heavyweight than probing by libvirt but I'm not sure, we
can listen to libvirt guys.

>
>
>
> > Or consider the case when USO is not supported by the kernel in the
> > destination, even if qemu reports this, I'm not sure what is expected
> > to be done in the management layer?
> >
> > Thanks
>
> reports what?

USO is not supported by this kernel.

Btw, to not make things worse, I would revert this until we find a
solution. Do you agree?

commit 1c79ab6937ae938d3dfd4da1c01afc7eb599857e
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Oct 10 16:12:57 2025 +0200

    virtio-net: Advertise UDP tunnel GSO support by default

    Allow bidirectional aggregated traffic for UDP encapsulated flows.

    Add the needed compatibility entries to avoid migration issues
    vs older QEMU instances.

    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Tested-by: Lei Yang <leiyang@redhat.com>
    Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Message-Id:
<9c500fbcd2cf29afd1826b1ac906f9d5beac3601.1760104079.git.pabeni@redhat.com>

Otherwise we will suffer from a similar issue soon.

Thanks

>
> --
> MST
>



      reply	other threads:[~2025-11-20  1:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07  2:01 [RFC PATCH] virtio-net: introduce strict peer feature check Jason Wang
2025-11-12 21:55 ` Peter Xu
2025-11-13  0:31   ` Jason Wang
2025-11-13 15:51     ` Peter Xu
2025-11-13  8:53   ` Daniel P. Berrangé
2025-11-13 15:58     ` Peter Xu
2025-11-13 16:09 ` Michael S. Tsirkin
2025-11-13 16:37   ` Peter Xu
2025-11-13 16:47     ` Michael S. Tsirkin
2025-11-13 17:12       ` Peter Xu
2025-11-13 17:46         ` Michael S. Tsirkin
2025-11-13 19:32           ` Peter Xu
2025-11-14  1:51             ` Jason Wang
2025-11-16  6:45               ` Michael S. Tsirkin
2025-11-19  2:06                 ` Jason Wang
2025-11-19  6:31                   ` Michael S. Tsirkin
2025-11-14  5:48             ` Thomas Huth
2025-11-14  9:53               ` Jinpu Wang
2025-11-14 15:47               ` Peter Xu
2025-11-14  1:32           ` Jason Wang
2025-11-16  6:52             ` Michael S. Tsirkin
2025-11-17  4:31               ` Jason Wang
2025-11-17  8:57                 ` Michael S. Tsirkin
2025-11-19  2:49                   ` Jason Wang
2025-11-19  8:07                     ` Michael S. Tsirkin
2025-11-20  1:45                       ` Jason Wang [this message]

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=CACGkMEusFr2Ge0GthiEkhwkZ6ncByrVFkL6BcTrHmCK4TmEiOA@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=farosas@suse.de \
    --cc=jinpu.wang@ionos.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wangyanan55@huawei.com \
    --cc=zhao1.liu@intel.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).