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 v2 1/6] virtio: Add bool to VirtQueueElement
Date: Wed, 22 May 2024 17:44:14 +0200 [thread overview]
Message-ID: <CAJaqyWcTh9YPMyitxoOZTxTjKishHCcNSz8wm1B2FRG4YdYGFg@mail.gmail.com> (raw)
In-Reply-To: <20240520130048.1483177-2-jonah.palmer@oracle.com>
On Mon, May 20, 2024 at 3:01 PM Jonah Palmer <jonah.palmer@oracle.com> wrote:
>
> Add the boolean 'in_order_filled' member to the VirtQueueElement structure.
> The use of this boolean will signify whether the element has been processed
> and is ready to be flushed (so long as the element is in-order). This
> boolean is used to support the VIRTIO_F_IN_ORDER feature.
>
> Tested-by: Lei Yang <leiyang@redhat.com>
The code has changed from the version that Lei tested, so we should
drop this tag until he re-test again.
Reviewed-by: Eugenio Pérez <eperezma@redhat.com>
> Signed-off-by: Jonah Palmer <jonah.palmer@oracle.com>
> ---
> include/hw/virtio/virtio.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index 7d5ffdc145..88e70c1ae1 100644
> --- a/include/hw/virtio/virtio.h
> +++ b/include/hw/virtio/virtio.h
> @@ -69,6 +69,8 @@ typedef struct VirtQueueElement
> unsigned int ndescs;
> unsigned int out_num;
> unsigned int in_num;
> + /* Element has been processed (VIRTIO_F_IN_ORDER) */
> + bool in_order_filled;
> hwaddr *in_addr;
> hwaddr *out_addr;
> struct iovec *in_sg;
> --
> 2.39.3
>
next prev parent reply other threads:[~2024-05-22 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 13:00 [PATCH v2 0/6] virtio,vhost: Add VIRTIO_F_IN_ORDER support Jonah Palmer
2024-05-20 13:00 ` [PATCH v2 1/6] virtio: Add bool to VirtQueueElement Jonah Palmer
2024-05-22 15:44 ` Eugenio Perez Martin [this message]
2024-05-23 9:55 ` Jonah Palmer
2024-05-20 13:00 ` [PATCH v2 2/6] virtio: virtqueue_pop - VIRTIO_F_IN_ORDER support Jonah Palmer
2024-05-22 15:45 ` Eugenio Perez Martin
2024-05-23 9:56 ` Jonah Palmer
2024-05-20 13:00 ` [PATCH v2 3/6] virtio: virtqueue_ordered_fill " Jonah Palmer
2024-05-22 16:07 ` Eugenio Perez Martin
2024-05-23 10:29 ` Jonah Palmer
2024-05-23 10:47 ` Eugenio Perez Martin
2024-05-23 11:10 ` Jonah Palmer
2024-05-20 13:00 ` [PATCH v2 4/6] virtio: virtqueue_ordered_flush " Jonah Palmer
2024-05-20 13:00 ` [PATCH v2 5/6] vhost, vhost-user: Add VIRTIO_F_IN_ORDER to vhost feature bits Jonah Palmer via
2024-05-20 13:00 ` [PATCH v2 6/6] virtio: Add VIRTIO_F_IN_ORDER property definition Jonah Palmer
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=CAJaqyWcTh9YPMyitxoOZTxTjKishHCcNSz8wm1B2FRG4YdYGFg@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).