From: Eugenio Perez Martin <eperezma@redhat.com>
To: Jonah Palmer <jonah.palmer@oracle.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, raphael@enfabrica.net,
kwolf@redhat.com, hreitz@redhat.com, jasowang@redhat.com,
pbonzini@redhat.com, fam@euphon.net, stefanha@redhat.com,
qemu-block@nongnu.org, schalla@marvell.com, leiyang@redhat.com,
virtio-fs@lists.linux.dev, si-wei.liu@oracle.com,
boris.ostrovsky@oracle.com
Subject: Re: [PATCH v4 4/6] virtio: virtqueue_ordered_flush - VIRTIO_F_IN_ORDER support
Date: Wed, 10 Jul 2024 18:16:35 +0200 [thread overview]
Message-ID: <CAJaqyWfRCAif9ou9XMCbDaKWPqt9msB7QbdbSGVkqTJv8O_McQ@mail.gmail.com> (raw)
In-Reply-To: <20240710125522.4168043-5-jonah.palmer@oracle.com>
On Wed, Jul 10, 2024 at 2:56 PM Jonah Palmer <jonah.palmer@oracle.com> wrote:
>
> Add VIRTIO_F_IN_ORDER feature support for the virtqueue_flush operation.
>
> The goal of the virtqueue_ordered_flush operation when the
> VIRTIO_F_IN_ORDER feature has been negotiated is to write elements to
> the used/descriptor ring in-order and then update used_idx.
>
> The function iterates through the VirtQueueElement used_elems array
> in-order starting at vq->used_idx. If the element is valid (filled), the
> element is written to the used/descriptor ring. This process continues
> until we find an invalid (not filled) element.
>
> For packed VQs, the first entry (at vq->used_idx) is written to the
> descriptor ring last so the guest doesn't see any invalid descriptors.
>
> If any elements were written, the used_idx is updated.
>
> Signed-off-by: Jonah Palmer <jonah.palmer@oracle.com>
Acked-by: Eugenio Pérez <eperezma@redhat.com>
> ---
> Several fixes here for the split VQ case:
> - Ensure all previous write operations to buffers are completed before
> updating the used_idx (via smp_wmb()).
>
> - used_elems index 'i' should be incremented by the number of descriptors
> in the current element we just processed, not by the running total of
> descriptors already seen. This would've caused batched operations to
> miss ordered elements when looping through the used_elems array.
>
> - Do not keep the VQ's used_idx bound between 0 and vring.num-1 when
> setting it via vring_used_idx_set().
>
> While the packed VQ case naturally keeps used_idx bound between 0 and
> vring.num-1, the split VQ case cannot. This is because used_idx is
> used to compare the current event index with the new and old used
> indices to decide if a notification is necessary (see
> virtio_split_should_notify()). This comparison expects used_idx to be
> between 0 and 65535, not 0 and vring.num-1.
>
> hw/virtio/virtio.c | 70 +++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 69 insertions(+), 1 deletion(-)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 0000a7b41c..b419d8d6e7 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -1023,6 +1023,72 @@ static void virtqueue_packed_flush(VirtQueue *vq, unsigned int count)
> }
> }
>
> +static void virtqueue_ordered_flush(VirtQueue *vq)
> +{
> + unsigned int i = vq->used_idx % vq->vring.num;
> + unsigned int ndescs = 0;
> + uint16_t old = vq->used_idx;
> + uint16_t new;
> + bool packed;
> + VRingUsedElem uelem;
> +
> + packed = virtio_vdev_has_feature(vq->vdev, VIRTIO_F_RING_PACKED);
> +
> + if (packed) {
> + if (unlikely(!vq->vring.desc)) {
> + return;
> + }
> + } else if (unlikely(!vq->vring.used)) {
> + return;
> + }
> +
> + /* First expected in-order element isn't ready, nothing to do */
> + if (!vq->used_elems[i].in_order_filled) {
> + return;
> + }
> +
> + /* Search for filled elements in-order */
> + while (vq->used_elems[i].in_order_filled) {
> + /*
> + * First entry for packed VQs is written last so the guest
> + * doesn't see invalid descriptors.
> + */
> + if (packed && i != vq->used_idx) {
> + virtqueue_packed_fill_desc(vq, &vq->used_elems[i], ndescs, false);
> + } else if (!packed) {
> + uelem.id = vq->used_elems[i].index;
> + uelem.len = vq->used_elems[i].len;
> + vring_used_write(vq, &uelem, i);
> + }
> +
> + vq->used_elems[i].in_order_filled = false;
> + ndescs += vq->used_elems[i].ndescs;
> + i += vq->used_elems[i].ndescs;
> + if (i >= vq->vring.num) {
> + i -= vq->vring.num;
> + }
> + }
> +
> + if (packed) {
> + virtqueue_packed_fill_desc(vq, &vq->used_elems[vq->used_idx], 0, true);
> + vq->used_idx += ndescs;
> + if (vq->used_idx >= vq->vring.num) {
> + vq->used_idx -= vq->vring.num;
> + vq->used_wrap_counter ^= 1;
> + vq->signalled_used_valid = false;
> + }
> + } else {
> + /* Make sure buffer is written before we update index. */
> + smp_wmb();
> + new = old + ndescs;
> + vring_used_idx_set(vq, new);
> + if (unlikely((int16_t)(new - vq->signalled_used) < (uint16_t)(new - old))) {
> + vq->signalled_used_valid = false;
> + }
> + }
> + vq->inuse -= ndescs;
> +}
> +
> void virtqueue_flush(VirtQueue *vq, unsigned int count)
> {
> if (virtio_device_disabled(vq->vdev)) {
> @@ -1030,7 +1096,9 @@ void virtqueue_flush(VirtQueue *vq, unsigned int count)
> return;
> }
>
> - if (virtio_vdev_has_feature(vq->vdev, VIRTIO_F_RING_PACKED)) {
> + if (virtio_vdev_has_feature(vq->vdev, VIRTIO_F_IN_ORDER)) {
> + virtqueue_ordered_flush(vq);
> + } else if (virtio_vdev_has_feature(vq->vdev, VIRTIO_F_RING_PACKED)) {
> virtqueue_packed_flush(vq, count);
> } else {
> virtqueue_split_flush(vq, count);
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-07-10 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 12:55 [PATCH v4 0/6] virtio,vhost: Add VIRTIO_F_IN_ORDER support Jonah Palmer
2024-07-10 12:55 ` [PATCH v4 1/6] virtio: Add bool to VirtQueueElement Jonah Palmer
2024-07-10 12:55 ` [PATCH v4 2/6] virtio: virtqueue_pop - VIRTIO_F_IN_ORDER support Jonah Palmer
2024-07-10 12:55 ` [PATCH v4 3/6] virtio: virtqueue_ordered_fill " Jonah Palmer
2024-07-10 12:55 ` [PATCH v4 4/6] virtio: virtqueue_ordered_flush " Jonah Palmer
2024-07-10 16:16 ` Eugenio Perez Martin [this message]
2024-07-10 12:55 ` [PATCH v4 5/6] vhost, vhost-user: Add VIRTIO_F_IN_ORDER to vhost feature bits Jonah Palmer via
2024-07-10 12:55 ` [PATCH v4 6/6] virtio: Add VIRTIO_F_IN_ORDER property definition Jonah Palmer
2024-07-20 19:16 ` Michael S. Tsirkin
2024-07-22 11:11 ` Eugenio Perez Martin
2024-07-22 11:31 ` 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=CAJaqyWfRCAif9ou9XMCbDaKWPqt9msB7QbdbSGVkqTJv8O_McQ@mail.gmail.com \
--to=eperezma@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jonah.palmer@oracle.com \
--cc=kwolf@redhat.com \
--cc=leiyang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael@enfabrica.net \
--cc=schalla@marvell.com \
--cc=si-wei.liu@oracle.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@lists.linux.dev \
/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).