Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Dragos Tatulea <dtatulea@nvidia.com>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	Tariq Toukan <tariqt@nvidia.com>,
	Shahar Shitrit <shshitrit@nvidia.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] vhost-vdpa: Expose ASID group change after DRIVER_OK via backend feature
Date: Mon, 27 Jul 2026 16:08:06 +0200	[thread overview]
Message-ID: <10ef2bf5-9232-4b0a-8a94-d7c84f8a0f0e@nvidia.com> (raw)
In-Reply-To: <89b04dff-3cc6-4ce7-8909-30552aed653d@nvidia.com>



On 29.06.26 11:39, Dragos Tatulea wrote:
> 
> 
> On 21.05.26 10:26, Eugenio Perez Martin wrote:
>> On Mon, May 11, 2026 at 11:46 AM Dragos Tatulea <dtatulea@nvidia.com> wrote:
>>>
>>> The commit in the fixes tag blocked VHOST_VDPA_SET_GROUP_ASID operations
>>> once DRIVER_OK is set. That is too strict for devices which can safely
>>> handle this during live migration flows.
>>>
>>> Bring back this behavior under a new vhost backend feature flag. The
>>> feature is supported by mlx5 and vdpa_sim devices.
>>>
>>> Fixes: 3543b04a4ea3 ("vhost: forbid change vq groups ASID if DRIVER_OK is set")
>>> Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
>>> Reviewed-by: Shahar Shitrit <shshitrit@nvidia.com>
>>
>> Acked-by: Eugenio Pérez <eperezma@redhat.com>
>>
>>> ---
>>>  drivers/vdpa/mlx5/net/mlx5_vnet.c |  3 ++-
>>>  drivers/vdpa/vdpa_sim/vdpa_sim.c  |  3 ++-
>>>  drivers/vhost/vdpa.c              | 13 +++++++++++--
>>>  include/uapi/linux/vhost_types.h  |  4 ++++
>>>  4 files changed, 19 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c b/drivers/vdpa/mlx5/net/mlx5_vnet.c
>>> index ad0d5fbbbca8..f89177957c76 100644
>>> --- a/drivers/vdpa/mlx5/net/mlx5_vnet.c
>>> +++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c
>>> @@ -2906,7 +2906,8 @@ static void unregister_link_notifier(struct mlx5_vdpa_net *ndev)
>>>
>>>  static u64 mlx5_vdpa_get_backend_features(const struct vdpa_device *vdpa)
>>>  {
>>> -       return BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK);
>>> +       return BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK) |
>>> +              BIT_ULL(VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK);
>>>  }
>>>
>>>  static int mlx5_vdpa_set_driver_features(struct vdpa_device *vdev, u64 features)
>>> diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c b/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>> index 8cb1cc2ea139..253c7fb35ea0 100644
>>> --- a/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>> +++ b/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>> @@ -428,7 +428,8 @@ static u64 vdpasim_get_device_features(struct vdpa_device *vdpa)
>>>
>>>  static u64 vdpasim_get_backend_features(const struct vdpa_device *vdpa)
>>>  {
>>> -       return BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK);
>>> +       return BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK) |
>>> +              BIT_ULL(VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK);
>>>  }
>>>
>>>  static int vdpasim_set_driver_features(struct vdpa_device *vdpa, u64 features)
>>> diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
>>> index 692564b1bcbb..67b3f49fa709 100644
>>> --- a/drivers/vhost/vdpa.c
>>> +++ b/drivers/vhost/vdpa.c
>>> @@ -682,7 +682,8 @@ static long vhost_vdpa_vring_ioctl(struct vhost_vdpa *v, unsigned int cmd,
>>>                         return -EFAULT;
>>>                 if (idx >= vdpa->ngroups || s.num >= vdpa->nas)
>>>                         return -EINVAL;
>>> -               if (ops->get_status(vdpa) & VIRTIO_CONFIG_S_DRIVER_OK)
>>> +               if ((ops->get_status(vdpa) & VIRTIO_CONFIG_S_DRIVER_OK) &&
>>> +                   !vhost_backend_has_feature(vq, VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK))
>>>                         return -EBUSY;
>>>                 if (!ops->set_group_asid)
>>>                         return -EOPNOTSUPP;
>>> @@ -791,7 +792,8 @@ static long vhost_vdpa_unlocked_ioctl(struct file *filep,
>>>                                  BIT_ULL(VHOST_BACKEND_F_IOTLB_PERSIST) |
>>>                                  BIT_ULL(VHOST_BACKEND_F_SUSPEND) |
>>>                                  BIT_ULL(VHOST_BACKEND_F_RESUME) |
>>> -                                BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK)))
>>> +                                BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK) |
>>> +                                BIT_ULL(VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK)))
>>>                         return -EOPNOTSUPP;
>>>                 if ((features & BIT_ULL(VHOST_BACKEND_F_SUSPEND)) &&
>>>                      !vhost_vdpa_can_suspend(v))
>>> @@ -805,6 +807,13 @@ static long vhost_vdpa_unlocked_ioctl(struct file *filep,
>>>                 if ((features & BIT_ULL(VHOST_BACKEND_F_DESC_ASID)) &&
>>>                      !vhost_vdpa_has_desc_group(v))
>>>                         return -EOPNOTSUPP;
>>
>> Ouch to me here. By reading the errno manual:
>>
>> Nit: By reading errno(3):
>> ENOTSUP - Operation not supported (POSIX.1-2001).
>> EOPNOTSUPP - Operation not supported on socket (POSIX.1-2001).
>>
>> I picked the wrong constant even if they share the same errno value
>> (by the same page of the manual). MST, is it worth changing it?
>>
>>> +               if (features & BIT_ULL(VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK)) {
>>> +                       if (!(features & BIT_ULL(VHOST_BACKEND_F_IOTLB_ASID)))
>>> +                               return -EINVAL;
>>> +                       if (!(vhost_vdpa_get_backend_features(v) &
>>> +                               BIT_ULL(VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK)))
>>> +                               return -EOPNOTSUPP;
>>> +               }
>>>                 if ((features & BIT_ULL(VHOST_BACKEND_F_IOTLB_PERSIST)) &&
>>>                      !vhost_vdpa_has_persistent_map(v))
>>>                         return -EOPNOTSUPP;
>>> diff --git a/include/uapi/linux/vhost_types.h b/include/uapi/linux/vhost_types.h
>>> index 1c39cc5f5a31..ec1ff8a2e260 100644
>>> --- a/include/uapi/linux/vhost_types.h
>>> +++ b/include/uapi/linux/vhost_types.h
>>> @@ -197,5 +197,9 @@ struct vhost_vdpa_iova_range {
>>>  #define VHOST_BACKEND_F_DESC_ASID    0x7
>>>  /* IOTLB don't flush memory mapping across device reset */
>>>  #define VHOST_BACKEND_F_IOTLB_PERSIST  0x8
>>> +/* Device supports changing the group ASID after DRIVER_OK.
>>> + * Requires VHOST_BACKEND_F_IOTLB_ASID.
>>> + */
>>> +#define VHOST_BACKEND_F_GROUP_ASID_AFTER_DRIVER_OK  0x9
>>>
>>>  #endif
>>> --
>>> 2.54.0
>>>
>>
> 
> Gentle ping. Is this patch missing anything?
> 
One more ping.

Thanks,
Dragos

      reply	other threads:[~2026-07-27 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  9:45 [PATCH] vhost-vdpa: Expose ASID group change after DRIVER_OK via backend feature Dragos Tatulea
2026-05-21  7:14 ` Dragos Tatulea
2026-05-21  8:26 ` Eugenio Perez Martin
2026-06-29  9:39   ` Dragos Tatulea
2026-07-27 14:08     ` Dragos Tatulea [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=10ef2bf5-9232-4b0a-8a94-d7c84f8a0f0e@nvidia.com \
    --to=dtatulea@nvidia.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=shshitrit@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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