From: Jason Wang <jasowang@redhat.com>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: qemu-devel@nongnu.org, Parav Pandit <parav@mellanox.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Si-Wei Liu <si-wei.liu@oracle.com>,
Laurent Vivier <lvivier@redhat.com>,
Harpreet Singh Anand <hanand@xilinx.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Gautam Dawar <gdawar@xilinx.com>,
Liuxiangdong <liuxiangdong5@huawei.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Cindy Lu <lulu@redhat.com>, Eli Cohen <eli@mellanox.com>,
Cornelia Huck <cohuck@redhat.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
kvm@vger.kernel.org, "Gonglei (Arei)" <arei.gonglei@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v6 09/10] vdpa: Add listener_shadow_vq to vhost_vdpa
Date: Fri, 11 Nov 2022 15:48:58 +0800 [thread overview]
Message-ID: <be553273-7c06-78f7-4d23-de9f46a210b1@redhat.com> (raw)
In-Reply-To: <CAJaqyWemKoRNd6_uvFc79qYe+7pbavJSjnZuczxk5uxSZZdZ2Q@mail.gmail.com>
在 2022/11/10 21:47, Eugenio Perez Martin 写道:
> On Thu, Nov 10, 2022 at 7:01 AM Jason Wang <jasowang@redhat.com> wrote:
>> On Wed, Nov 9, 2022 at 1:08 AM Eugenio Pérez <eperezma@redhat.com> wrote:
>>> The memory listener that thells the device how to convert GPA to qemu's
>>> va is registered against CVQ vhost_vdpa. This series try to map the
>>> memory listener translations to ASID 0, while it maps the CVQ ones to
>>> ASID 1.
>>>
>>> Let's tell the listener if it needs to register them on iova tree or
>>> not.
>>>
>>> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
>>> ---
>>> v5: Solve conflict about vhost_iova_tree_remove accepting mem_region by
>>> value.
>>> ---
>>> include/hw/virtio/vhost-vdpa.h | 2 ++
>>> hw/virtio/vhost-vdpa.c | 6 +++---
>>> net/vhost-vdpa.c | 1 +
>>> 3 files changed, 6 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/include/hw/virtio/vhost-vdpa.h b/include/hw/virtio/vhost-vdpa.h
>>> index 6560bb9d78..0c3ed2d69b 100644
>>> --- a/include/hw/virtio/vhost-vdpa.h
>>> +++ b/include/hw/virtio/vhost-vdpa.h
>>> @@ -34,6 +34,8 @@ typedef struct vhost_vdpa {
>>> struct vhost_vdpa_iova_range iova_range;
>>> uint64_t acked_features;
>>> bool shadow_vqs_enabled;
>>> + /* The listener must send iova tree addresses, not GPA */
Btw, cindy's vIOMMU series will make it not necessarily GPA any more.
>>> + bool listener_shadow_vq;
>>> /* IOVA mapping used by the Shadow Virtqueue */
>>> VhostIOVATree *iova_tree;
>>> GPtrArray *shadow_vqs;
>>> diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
>>> index 8fd32ba32b..e3914fa40e 100644
>>> --- a/hw/virtio/vhost-vdpa.c
>>> +++ b/hw/virtio/vhost-vdpa.c
>>> @@ -220,7 +220,7 @@ static void vhost_vdpa_listener_region_add(MemoryListener *listener,
>>> vaddr, section->readonly);
>>>
>>> llsize = int128_sub(llend, int128_make64(iova));
>>> - if (v->shadow_vqs_enabled) {
>>> + if (v->listener_shadow_vq) {
>>> int r;
>>>
>>> mem_region.translated_addr = (hwaddr)(uintptr_t)vaddr,
>>> @@ -247,7 +247,7 @@ static void vhost_vdpa_listener_region_add(MemoryListener *listener,
>>> return;
>>>
>>> fail_map:
>>> - if (v->shadow_vqs_enabled) {
>>> + if (v->listener_shadow_vq) {
>>> vhost_iova_tree_remove(v->iova_tree, mem_region);
>>> }
>>>
>>> @@ -292,7 +292,7 @@ static void vhost_vdpa_listener_region_del(MemoryListener *listener,
>>>
>>> llsize = int128_sub(llend, int128_make64(iova));
>>>
>>> - if (v->shadow_vqs_enabled) {
>>> + if (v->listener_shadow_vq) {
>>> const DMAMap *result;
>>> const void *vaddr = memory_region_get_ram_ptr(section->mr) +
>>> section->offset_within_region +
>>> diff --git a/net/vhost-vdpa.c b/net/vhost-vdpa.c
>>> index 85a318faca..02780ee37b 100644
>>> --- a/net/vhost-vdpa.c
>>> +++ b/net/vhost-vdpa.c
>>> @@ -570,6 +570,7 @@ static NetClientState *net_vhost_vdpa_init(NetClientState *peer,
>>> s->vhost_vdpa.index = queue_pair_index;
>>> s->always_svq = svq;
>>> s->vhost_vdpa.shadow_vqs_enabled = svq;
>>> + s->vhost_vdpa.listener_shadow_vq = svq;
>> Any chance those above two can differ?
>>
> If CVQ is shadowed but data VQs are not, shadow_vqs_enabled is true
> but listener_shadow_vq is not.
>
> It is more clear in the next commit, where only shadow_vqs_enabled is
> set to true at vhost_vdpa_net_cvq_start.
Ok, the name looks a little bit confusing. I wonder if it's better to
use shadow_cvq and shadow_data ?
Thanks
>
> Thanks!
>
>> Thanks
>>
>>> s->vhost_vdpa.iova_tree = iova_tree;
>>> if (!is_datapath) {
>>> s->cvq_cmd_out_buffer = qemu_memalign(qemu_real_host_page_size(),
>>> --
>>> 2.31.1
>>>
next prev parent reply other threads:[~2022-11-11 7:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 17:07 [PATCH v6 00/10] ASID support in vhost-vdpa net Eugenio Pérez
2022-11-08 17:07 ` [PATCH v6 01/10] vdpa: Use v->shadow_vqs_enabled in vhost_vdpa_svqs_start & stop Eugenio Pérez
2022-11-10 5:21 ` Jason Wang
2022-11-10 12:54 ` Eugenio Perez Martin
2022-11-11 7:24 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 02/10] vhost: set SVQ device call handler at SVQ start Eugenio Pérez
2022-11-10 5:22 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 03/10] vhost: Allocate SVQ device file descriptors at device start Eugenio Pérez
2022-11-10 5:28 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 04/10] vdpa: add vhost_vdpa_net_valid_svq_features Eugenio Pérez
2022-11-10 5:29 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 05/10] vdpa: move SVQ vring features check to net/ Eugenio Pérez
2022-11-10 5:40 ` Jason Wang
2022-11-10 13:09 ` Eugenio Perez Martin
2022-11-11 7:34 ` Jason Wang
2022-11-11 7:55 ` Eugenio Perez Martin
2022-11-11 8:07 ` Jason Wang
2022-11-11 12:58 ` Eugenio Perez Martin
2022-11-14 4:26 ` Jason Wang
2022-11-14 10:10 ` Eugenio Perez Martin
2022-11-08 17:07 ` [PATCH v6 06/10] vdpa: Allocate SVQ unconditionally Eugenio Pérez
2022-11-08 17:07 ` [PATCH v6 07/10] vdpa: Add asid parameter to vhost_vdpa_dma_map/unmap Eugenio Pérez
2022-11-10 5:50 ` Jason Wang
2022-11-10 13:22 ` Eugenio Perez Martin
2022-11-11 7:41 ` Jason Wang
2022-11-11 13:02 ` Eugenio Perez Martin
2022-11-14 4:27 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 08/10] vdpa: Store x-svq parameter in VhostVDPAState Eugenio Pérez
2022-11-08 17:07 ` [PATCH v6 09/10] vdpa: Add listener_shadow_vq to vhost_vdpa Eugenio Pérez
2022-11-10 6:00 ` Jason Wang
2022-11-10 13:47 ` Eugenio Perez Martin
2022-11-11 7:48 ` Jason Wang [this message]
2022-11-11 13:12 ` Eugenio Perez Martin
2022-11-14 4:30 ` Jason Wang
2022-11-14 16:30 ` Eugenio Perez Martin
2022-11-15 3:04 ` Jason Wang
2022-11-15 11:24 ` Eugenio Perez Martin
2022-11-16 3:33 ` Jason Wang
2022-11-08 17:07 ` [PATCH v6 10/10] vdpa: Always start CVQ in SVQ mode Eugenio Pérez
2022-11-10 6:24 ` Jason Wang
2022-11-10 16:07 ` Eugenio Perez Martin
2022-11-11 8:02 ` Jason Wang
2022-11-11 14:38 ` Eugenio Perez Martin
2022-11-14 4:36 ` Jason Wang
2022-11-10 12:25 ` [PATCH v6 00/10] ASID support in vhost-vdpa net Michael S. Tsirkin
2022-11-10 12:56 ` Eugenio Perez Martin
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=be553273-7c06-78f7-4d23-de9f46a210b1@redhat.com \
--to=jasowang@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=cohuck@redhat.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=liuxiangdong5@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).