netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	 Shannon Nelson <shannon.nelson@amd.com>
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, "Jason Wang" <jasowang@redhat.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"Tiwei Bie" <tiwei.bie@intel.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost-vdpa: filter VIRTIO_F_RING_PACKED feature
Date: Mon, 5 Jun 2023 15:30:35 +0200	[thread overview]
Message-ID: <gi2hngx3ndsgz5d2rpqjywdmou5vxhd7xgi5z2lbachr7yoos4@kpifz37oz2et> (raw)
In-Reply-To: <20230605085840-mutt-send-email-mst@kernel.org>

On Mon, Jun 05, 2023 at 09:00:25AM -0400, Michael S. Tsirkin wrote:
>On Mon, Jun 05, 2023 at 02:54:20PM +0200, Stefano Garzarella wrote:
>> On Mon, Jun 05, 2023 at 08:41:54AM -0400, Michael S. Tsirkin wrote:
>> > On Mon, Jun 05, 2023 at 01:06:44PM +0200, Stefano Garzarella wrote:
>> > > vhost-vdpa IOCTLs (eg. VHOST_GET_VRING_BASE, VHOST_SET_VRING_BASE)
>> > > don't support packed virtqueue well yet, so let's filter the
>> > > VIRTIO_F_RING_PACKED feature for now in vhost_vdpa_get_features().
>> > >
>> > > This way, even if the device supports it, we don't risk it being
>> > > negotiated, then the VMM is unable to set the vring state properly.
>> > >
>> > > Fixes: 4c8cf31885f6 ("vhost: introduce vDPA-based backend")
>> > > Cc: stable@vger.kernel.org
>> > > Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>> > > ---
>> > >
>> > > Notes:
>> > >     This patch should be applied before the "[PATCH v2 0/3] vhost_vdpa:
>> > >     better PACKED support" series [1] and backported in stable branches.
>> > >
>> > >     We can revert it when we are sure that everything is working with
>> > >     packed virtqueues.
>> > >
>> > >     Thanks,
>> > >     Stefano
>> > >
>> > >     [1] https://lore.kernel.org/virtualization/20230424225031.18947-1-shannon.nelson@amd.com/
>> >
>> > I'm a bit lost here. So why am I merging "better PACKED support" then?
>>
>> To really support packed virtqueue with vhost-vdpa, at that point we would
>> also have to revert this patch.
>>
>> I wasn't sure if you wanted to queue the series for this merge window.
>> In that case do you think it is better to send this patch only for stable
>> branches?
>> > Does this patch make them a NOP?
>>
>> Yep, after applying the "better PACKED support" series and being sure 
>> that
>> the IOCTLs of vhost-vdpa support packed virtqueue, we should revert this
>> patch.
>>
>> Let me know if you prefer a different approach.
>>
>> I'm concerned that QEMU uses vhost-vdpa IOCTLs thinking that the kernel
>> interprets them the right way, when it does not.
>>
>> Thanks,
>> Stefano
>>
>
>If this fixes a bug can you add Fixes tags to each of them? Then it's ok
>to merge in this window. Probably easier than the elaborate
>mask/unmask dance.

CCing Shannon (the original author of the "better PACKED support"
series).

IIUC Shannon is going to send a v3 of that series to fix the
documentation, so Shannon can you also add the Fixes tags?

Thanks,
Stefano


  reply	other threads:[~2023-06-05 13:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 11:06 [PATCH] vhost-vdpa: filter VIRTIO_F_RING_PACKED feature Stefano Garzarella
2023-06-05 12:41 ` Michael S. Tsirkin
2023-06-05 12:54   ` Stefano Garzarella
2023-06-05 13:00     ` Michael S. Tsirkin
2023-06-05 13:30       ` Stefano Garzarella [this message]
2023-06-05 13:54         ` Michael S. Tsirkin
2023-06-05 14:56           ` Stefano Garzarella
2023-06-05 21:44             ` Michael S. Tsirkin
2023-06-06 10:09               ` Stefano Garzarella
2023-06-07 20:52                 ` Michael S. Tsirkin
2023-06-06  1:29             ` Jason Wang
2023-06-06 10:18               ` Stefano Garzarella
2023-06-06 12:58               ` Michael S. Tsirkin
2023-06-07  8:39                 ` Stefano Garzarella
2023-06-07  9:43                   ` Michael S. Tsirkin
2023-06-08  0:42                     ` Jason Wang
2023-06-08  6:03                       ` Michael S. Tsirkin
2023-06-08  7:46                         ` Jason Wang
2023-06-08  7:59                           ` Stefano Garzarella
2023-06-08  9:00                             ` Jason Wang
2023-06-08  9:21                               ` Stefano Garzarella
2023-06-08  9:29                                 ` Jason Wang
2023-06-08  9:47                                   ` Stefano Garzarella
2023-06-08 14:23                                   ` Michael S. Tsirkin
2023-06-09  2:16                                     ` Jason Wang
2023-06-09  7:17                                       ` Michael S. Tsirkin
2023-06-09  7:37                                     ` Stefano Garzarella
2023-06-08 13:46                               ` Michael S. Tsirkin
2023-06-08 13:43                           ` Michael S. Tsirkin
2023-06-22 11:37 ` Michael S. Tsirkin
2023-06-22 12:28   ` Stefano Garzarella

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=gi2hngx3ndsgz5d2rpqjywdmou5vxhd7xgi5z2lbachr7yoos4@kpifz37oz2et \
    --to=sgarzare@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@amd.com \
    --cc=tiwei.bie@intel.com \
    --cc=virtualization@lists.linux-foundation.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).