From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>, qemu-devel@nongnu.org
Cc: Parav Pandit <parav@mellanox.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
virtualization@lists.linux-foundation.org,
Harpreet Singh Anand <hanand@xilinx.com>,
Xiao W Wang <xiao.w.wang@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Eli Cohen <eli@mellanox.com>, Eric Blake <eblake@redhat.com>,
Michael Lilja <ml@napatech.com>
Subject: Re: [RFC PATCH v4 12/20] virtio: Add vhost_shadow_vq_get_vring_addr
Date: Wed, 13 Oct 2021 11:54:37 +0800 [thread overview]
Message-ID: <981f5647-544e-f35e-4b72-06eca733368f@redhat.com> (raw)
In-Reply-To: <20211001070603.307037-13-eperezma@redhat.com>
在 2021/10/1 下午3:05, Eugenio Pérez 写道:
> It reports the shadow virtqueue address from qemu virtual address space
I think both the title and commit log needs to more tweaks. Looking at
the codes, what id does is actually introduce vring into svq.
>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---
> hw/virtio/vhost-shadow-virtqueue.h | 4 +++
> hw/virtio/vhost-shadow-virtqueue.c | 50 ++++++++++++++++++++++++++++++
> 2 files changed, 54 insertions(+)
>
> diff --git a/hw/virtio/vhost-shadow-virtqueue.h b/hw/virtio/vhost-shadow-virtqueue.h
> index 237cfceb9c..2df3d117f5 100644
> --- a/hw/virtio/vhost-shadow-virtqueue.h
> +++ b/hw/virtio/vhost-shadow-virtqueue.h
> @@ -16,6 +16,10 @@ typedef struct VhostShadowVirtqueue VhostShadowVirtqueue;
>
> EventNotifier *vhost_svq_get_svq_call_notifier(VhostShadowVirtqueue *svq);
> void vhost_svq_set_guest_call_notifier(VhostShadowVirtqueue *svq, int call_fd);
> +void vhost_svq_get_vring_addr(const VhostShadowVirtqueue *svq,
> + struct vhost_vring_addr *addr);
> +size_t vhost_svq_driver_area_size(const VhostShadowVirtqueue *svq);
> +size_t vhost_svq_device_area_size(const VhostShadowVirtqueue *svq);
>
> bool vhost_svq_start(struct vhost_dev *dev, unsigned idx,
> VhostShadowVirtqueue *svq);
> diff --git a/hw/virtio/vhost-shadow-virtqueue.c b/hw/virtio/vhost-shadow-virtqueue.c
> index 3fe129cf63..5c1899f6af 100644
> --- a/hw/virtio/vhost-shadow-virtqueue.c
> +++ b/hw/virtio/vhost-shadow-virtqueue.c
> @@ -18,6 +18,9 @@
>
> /* Shadow virtqueue to relay notifications */
> typedef struct VhostShadowVirtqueue {
> + /* Shadow vring */
> + struct vring vring;
> +
> /* Shadow kick notifier, sent to vhost */
> EventNotifier kick_notifier;
> /* Shadow call notifier, sent to vhost */
> @@ -38,6 +41,9 @@ typedef struct VhostShadowVirtqueue {
>
> /* Virtio queue shadowing */
> VirtQueue *vq;
> +
> + /* Virtio device */
> + VirtIODevice *vdev;
> } VhostShadowVirtqueue;
>
> /* Forward guest notifications */
> @@ -93,6 +99,35 @@ void vhost_svq_set_guest_call_notifier(VhostShadowVirtqueue *svq, int call_fd)
> event_notifier_init_fd(&svq->guest_call_notifier, call_fd);
> }
>
> +/*
> + * Get the shadow vq vring address.
> + * @svq Shadow virtqueue
> + * @addr Destination to store address
> + */
> +void vhost_svq_get_vring_addr(const VhostShadowVirtqueue *svq,
> + struct vhost_vring_addr *addr)
> +{
> + addr->desc_user_addr = (uint64_t)svq->vring.desc;
> + addr->avail_user_addr = (uint64_t)svq->vring.avail;
> + addr->used_user_addr = (uint64_t)svq->vring.used;
> +}
> +
> +size_t vhost_svq_driver_area_size(const VhostShadowVirtqueue *svq)
> +{
> + uint16_t vq_idx = virtio_get_queue_index(svq->vq);
> + size_t desc_size = virtio_queue_get_desc_size(svq->vdev, vq_idx);
> + size_t avail_size = virtio_queue_get_avail_size(svq->vdev, vq_idx);
> +
> + return ROUND_UP(desc_size + avail_size, qemu_real_host_page_size);
Is this round up required by the spec?
> +}
> +
> +size_t vhost_svq_device_area_size(const VhostShadowVirtqueue *svq)
> +{
> + uint16_t vq_idx = virtio_get_queue_index(svq->vq);
> + size_t used_size = virtio_queue_get_used_size(svq->vdev, vq_idx);
> + return ROUND_UP(used_size, qemu_real_host_page_size);
> +}
> +
> /*
> * Restore the vhost guest to host notifier, i.e., disables svq effect.
> */
> @@ -178,6 +213,10 @@ void vhost_svq_stop(struct vhost_dev *dev, unsigned idx,
> VhostShadowVirtqueue *vhost_svq_new(struct vhost_dev *dev, int idx)
> {
> int vq_idx = dev->vq_index + idx;
> + unsigned num = virtio_queue_get_num(dev->vdev, vq_idx);
> + size_t desc_size = virtio_queue_get_desc_size(dev->vdev, vq_idx);
> + size_t driver_size;
> + size_t device_size;
> g_autofree VhostShadowVirtqueue *svq = g_new0(VhostShadowVirtqueue, 1);
> int r;
>
> @@ -196,6 +235,15 @@ VhostShadowVirtqueue *vhost_svq_new(struct vhost_dev *dev, int idx)
> }
>
> svq->vq = virtio_get_queue(dev->vdev, vq_idx);
> + svq->vdev = dev->vdev;
> + driver_size = vhost_svq_driver_area_size(svq);
> + device_size = vhost_svq_device_area_size(svq);
> + svq->vring.num = num;
> + svq->vring.desc = qemu_memalign(qemu_real_host_page_size, driver_size);
> + svq->vring.avail = (void *)((char *)svq->vring.desc + desc_size);
> + memset(svq->vring.desc, 0, driver_size);
Any reason for using the contiguous area for both desc and avail?
Thanks
> + svq->vring.used = qemu_memalign(qemu_real_host_page_size, device_size);
> + memset(svq->vring.used, 0, device_size);
> event_notifier_set_handler(&svq->call_notifier,
> vhost_svq_handle_call);
> return g_steal_pointer(&svq);
> @@ -215,5 +263,7 @@ void vhost_svq_free(VhostShadowVirtqueue *vq)
> event_notifier_cleanup(&vq->kick_notifier);
> event_notifier_set_handler(&vq->call_notifier, NULL);
> event_notifier_cleanup(&vq->call_notifier);
> + qemu_vfree(vq->vring.desc);
> + qemu_vfree(vq->vring.used);
> g_free(vq);
> }
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-10-13 3:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211001070603.307037-1-eperezma@redhat.com>
2021-10-12 3:59 ` [RFC PATCH v4 00/20] vDPA shadow virtqueue Jason Wang
2021-10-12 4:06 ` Jason Wang
[not found] ` <20211001070603.307037-9-eperezma@redhat.com>
2021-10-13 3:27 ` [RFC PATCH v4 08/20] vhost: Route guest->host notification through " Jason Wang
[not found] ` <CAJaqyWd2joWx3kKz=cJBs4UxZofP7ETkbpg9+cSQSE2MSyBtUg@mail.gmail.com>
2021-10-15 3:45 ` Jason Wang
[not found] ` <20211001070603.307037-10-eperezma@redhat.com>
2021-10-13 3:43 ` [RFC PATCH v4 09/20] vdpa: Save call_fd in vhost-vdpa Jason Wang
[not found] ` <20211001070603.307037-11-eperezma@redhat.com>
2021-10-13 3:43 ` [RFC PATCH v4 10/20] vhost-vdpa: Take into account SVQ in vhost_vdpa_set_vring_call Jason Wang
[not found] ` <20211001070603.307037-12-eperezma@redhat.com>
2021-10-13 3:47 ` [RFC PATCH v4 11/20] vhost: Route host->guest notification through shadow virtqueue Jason Wang
[not found] ` <CAJaqyWfm734HrwTJK71hUQNYVkyDaR8OiqtGro_AX9i_pXfmBQ@mail.gmail.com>
2021-10-15 4:42 ` Jason Wang
[not found] ` <CAJaqyWcO9oaGsRe-oMNbmHx7G4Mw0vZfc+7WYQ23+SteoFVn4Q@mail.gmail.com>
2021-10-20 2:01 ` Jason Wang
2021-10-13 3:49 ` Jason Wang
[not found] ` <CAJaqyWcQ314RN7-U1bYqCMXb+-nyhSi3ddqWv90ofFucMbveUw@mail.gmail.com>
2021-10-15 4:24 ` Jason Wang
[not found] ` <20211001070603.307037-13-eperezma@redhat.com>
2021-10-13 3:54 ` Jason Wang [this message]
[not found] ` <20211001070603.307037-14-eperezma@redhat.com>
2021-10-13 3:56 ` [RFC PATCH v4 13/20] vdpa: Save host and guest features Jason Wang
[not found] ` <20211001070603.307037-16-eperezma@redhat.com>
2021-10-13 4:31 ` [RFC PATCH v4 15/20] vhost: Shadow virtqueue buffers forwarding Jason Wang
[not found] ` <CAJaqyWeaJyxh-tt45wxONzuOLhVt6wO48e2ufZZ3uECHTDofFw@mail.gmail.com>
2021-10-15 4:23 ` Jason Wang
[not found] ` <20211001070603.307037-17-eperezma@redhat.com>
2021-10-13 4:35 ` [RFC PATCH v4 16/20] vhost: Check for device VRING_USED_F_NO_NOTIFY at shadow virtqueue kick Jason Wang
[not found] ` <20211001070603.307037-18-eperezma@redhat.com>
2021-10-13 4:36 ` [RFC PATCH v4 17/20] vhost: Use VRING_AVAIL_F_NO_INTERRUPT at device call on shadow virtqueue Jason Wang
[not found] ` <20211001070603.307037-19-eperezma@redhat.com>
2021-10-19 8:32 ` [RFC PATCH v4 18/20] vhost: Add VhostIOVATree Jason Wang
[not found] ` <20211001070603.307037-21-eperezma@redhat.com>
2021-10-13 5:34 ` [RFC PATCH v4 20/20] vdpa: Add custom IOTLB translations to SVQ Jason Wang
[not found] ` <CAJaqyWdEGWFNrxqKxRya=ybRiP0wTZ0aPksBBeOe9KOjOmUnqA@mail.gmail.com>
2021-10-15 7:37 ` Jason Wang
[not found] ` <CAJaqyWf7pFiw2twq9BPyr9fOJFa9ZpSMcbnoknOfC_pbuUWkmg@mail.gmail.com>
2021-10-15 8:37 ` Jason Wang
2021-10-19 9:24 ` Jason Wang
[not found] ` <CAJaqyWcRcm9rwuTqJHS0FmuMrXpoCvF34TzXKQmxXTfZssZ-jA@mail.gmail.com>
2021-10-20 2:02 ` Jason Wang
2021-10-20 2:07 ` Jason Wang
[not found] ` <CAJaqyWe6R_32Se75XF3+NUZyiWr+cLYQ_86LExmom-vCRT9G0g@mail.gmail.com>
2021-10-20 9:03 ` Jason Wang
[not found] ` <CAJaqyWd9LjpA5w2f1s+pNmdNjYPvcbJgPqY+Qv1fWb+6LPPzAg@mail.gmail.com>
2021-10-21 2:38 ` Jason Wang
2021-10-26 4:32 ` Jason Wang
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=981f5647-544e-f35e-4b72-06eca733368f@redhat.com \
--to=jasowang@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=hanand@xilinx.com \
--cc=ml@napatech.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiao.w.wang@intel.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).