patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: dev@dpdk.org, Chenbo Xia <chenbox@nvidia.com>,
	stable@dpdk.org,  Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH 0/2] Search the split vq desc and avail in RO areas
Date: Thu, 5 Jun 2025 13:50:41 +0200	[thread overview]
Message-ID: <CAJFAV8ydHHbbtOYLq4dr+g9qPh52EnNEZU5kieNAY4_BPfsO2A@mail.gmail.com> (raw)
In-Reply-To: <20250605113552.918120-1-eperezma@redhat.com>

On Thu, Jun 5, 2025 at 1:36 PM Eugenio Pérez <eperezma@redhat.com> 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.
>
> Eugenio Pérez (2):
>   vhost: search the split vq desc and avail in RO areas
>   vhost: search the packed vq driver area in RO areas
>
>  lib/vhost/vhost.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

At a quick glance, no need for two patches.

Sorry, the implication of this issue is not clear to me.
What is the impact from a user pov?


-- 
David Marchand


  parent reply	other threads:[~2025-06-05 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 11:35 Eugenio Pérez
2025-06-05 11:35 ` [PATCH 1/2] vhost: search " Eugenio Pérez
2025-06-05 11:35 ` [PATCH 2/2] vhost: search the packed vq driver area " Eugenio Pérez
2025-06-05 11:50 ` David Marchand [this message]
2025-06-05 14:54   ` [PATCH 0/2] Search the split vq desc and avail " Eugenio Perez Martin
2025-06-06 14:20     ` David Marchand
2025-06-06 15:10       ` 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=CAJFAV8ydHHbbtOYLq4dr+g9qPh52EnNEZU5kieNAY4_BPfsO2A@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=eperezma@redhat.com \
    --cc=maxime.coquelin@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).