DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>, dev@dpdk.org
Cc: Chenbo Xia <chenbox@nvidia.com>, stable@dpdk.org
Subject: Re: [PATCH 1/2] vhost: search the split vq desc and avail in RO areas
Date: Thu, 12 Jun 2025 15:55:45 +0200	[thread overview]
Message-ID: <be8da555-af1c-47af-8225-f5b43d8b6dbf@redhat.com> (raw)
In-Reply-To: <20250605113552.918120-2-eperezma@redhat.com>



On 6/5/25 1:35 PM, Eugenio Pérez wrote:
> QEMU's shadow virtqueue and VDUSE exposes these areas as read-only. If
> we don't change it, vhost_iova_to_vva do not consider them as valid and
> returns that they're not found.
> 
> Fixes: eefac9536a90 ("vhost: postpone device creation until rings are mapped")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---
>   lib/vhost/vhost.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/vhost/vhost.c b/lib/vhost/vhost.c
> index 0353a04dc8..95a99bace6 100644
> --- a/lib/vhost/vhost.c
> +++ b/lib/vhost/vhost.c
> @@ -497,7 +497,7 @@ vring_translate_split(struct virtio_net *dev, struct vhost_virtqueue *vq)
>   	size = req_size;
>   	vq->desc = (struct vring_desc *)(uintptr_t)vhost_iova_to_vva(dev, vq,
>   						vq->ring_addrs.desc_user_addr,
> -						&size, VHOST_ACCESS_RW);
> +						&size, VHOST_ACCESS_RO);
>   	if (!vq->desc || size != req_size)
>   		return -1;
>   
> @@ -508,7 +508,7 @@ vring_translate_split(struct virtio_net *dev, struct vhost_virtqueue *vq)
>   	size = req_size;
>   	vq->avail = (struct vring_avail *)(uintptr_t)vhost_iova_to_vva(dev, vq,
>   						vq->ring_addrs.avail_user_addr,
> -						&size, VHOST_ACCESS_RW);
> +						&size, VHOST_ACCESS_RO);
>   	if (!vq->avail || size != req_size)
>   		return -1;
>   

I propose below text for the commit message:

"
The virtqueues driver areas are read-only for the device.
While they are exposed as Read/Write to Vhost-user and regular VDUSE
backends, they are only exposed as Read-only when the control Virtqueue
is shadowed by QEMU with VDUSE backend.

This patch makes the backend to request these areas as Read-only, so 
that it can be accessed in all the configurations.
"

Also, as requested by David, patch 2 will be squashed into this one.

Eugenio, is that Ok for you?

With above suggested changes:
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2025-06-12 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 11:35 [PATCH 0/2] Search " Eugenio Pérez
2025-06-05 11:35 ` [PATCH 1/2] vhost: search " Eugenio Pérez
2025-06-12 13:55   ` Maxime Coquelin [this message]
2025-06-12 14:39     ` Eugenio Perez Martin
2025-06-05 11:35 ` [PATCH 2/2] vhost: search the packed vq driver area " Eugenio Pérez
2025-06-13  8:07   ` Maxime Coquelin
2025-06-05 11:50 ` [PATCH 0/2] Search the split vq desc and avail " David Marchand
2025-06-05 14:54   ` Eugenio Perez Martin
2025-06-06 14:20     ` David Marchand
2025-06-06 15:10       ` Maxime Coquelin
2025-06-13  8:07 ` Maxime Coquelin

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=be8da555-af1c-47af-8225-f5b43d8b6dbf@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=eperezma@redhat.com \
    --cc=stable@dpdk.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).