From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
Eugenio Perez Martin <eperezma@redhat.com>
Cc: dev@dpdk.org, Chenbo Xia <chenbox@nvidia.com>, stable@dpdk.org
Subject: Re: [PATCH 0/2] Search the split vq desc and avail in RO areas
Date: Fri, 6 Jun 2025 17:10:32 +0200 [thread overview]
Message-ID: <5076b1c0-1848-405c-ae27-00e3505a2733@redhat.com> (raw)
In-Reply-To: <CAJFAV8wnM+xNLrUbuYbJ7cJY+ZRKN5VcnBKwOtc_HHxj-YoaTg@mail.gmail.com>
On 6/6/25 4:20 PM, David Marchand wrote:
> On Thu, Jun 5, 2025 at 4:55 PM Eugenio Perez Martin <eperezma@redhat.com> wrote:
>>
>> On Thu, Jun 5, 2025 at 1:50 PM David Marchand <david.marchand@redhat.com> wrote:
>>>
>>> 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.
>>>
>>
>> Sure I can respin with both squashed.
>>
>>> Sorry, the implication of this issue is not clear to me.
>>> What is the impact from a user pov?
>>>
>>
>> QEMU maps the CVQ descriptors and avail vring through as read only
>> maps in the case of vDPA. But DPDK is looking for them with RW
>> permissions, so the vhost_iova_to_vva function never selects the right
>> one as valid.
>>
>> Looking for them with RO still picks the map if it is mapped as RW,
>> but the reverse is not true.
>
> Ok, thanks.
> Well, it's better, but still hard to tell how this impacts existing
> usecases :-).
> After discussing with Maxime, I understand that the shadow CVQ just
> can't work => blocking multi queue support with vduse for example.
> This is the type of high level impact I was looking for.
>
>> Let me know if you want me to respin the series with this comment too!
>
> Ideally yes, but maybe Maxime can do it when applying.
>
>
Yes, I can rework the commit message while applying.
Thanks,
Maxime
prev parent reply other threads:[~2025-06-06 15:10 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 ` [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 [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=5076b1c0-1848-405c-ae27-00e3505a2733@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.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).