From: Eric Farman <farman@linux.ibm.com>
To: Jonah Palmer <jonah.palmer@oracle.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, jasowang@redhat.com, eperezma@redhat.com,
si-wei.liu@oracle.com, boris.ostrovsky@oracle.com,
raphael@enfabrica.net, kwolf@redhat.com, hreitz@redhat.com,
pasic@linux.ibm.com, borntraeger@linux.ibm.com, thuth@redhat.com,
richard.henderson@linaro.org, david@redhat.com,
iii@linux.ibm.com, cohuck@redhat.com, pbonzini@redhat.com,
fam@euphon.net, stefanha@redhat.com, qemu-block@nongnu.org,
qemu-s390x@nongnu.org, virtio-fs@lists.linux.dev
Subject: Re: [PATCH v1 5/8] virtio-ccw: Handle extra notification data
Date: Mon, 11 Mar 2024 11:55:02 -0400 [thread overview]
Message-ID: <fc53c5567644a8fdd7ca06c89a20b7c52ddb574e.camel@linux.ibm.com> (raw)
In-Reply-To: <20240304194612.611660-6-jonah.palmer@oracle.com>
On Mon, 2024-03-04 at 14:46 -0500, Jonah Palmer wrote:
> > Add support to virtio-ccw devices for handling the extra data sent
> > from
> > the driver to the device when the VIRTIO_F_NOTIFICATION_DATA
> > transport
> > feature has been negotiated.
> >
> > The extra data that's passed to the virtio-ccw device when this
> > feature
> > is enabled varies depending on the device's virtqueue layout.
> >
> > That data passed to the virtio-ccw device is in the same format as
> > the
> > data passed to virtio-pci devices.
> >
> > Acked-by: Thomas Huth <thuth@redhat.com>
> > Signed-off-by: Jonah Palmer <jonah.palmer@oracle.com>
> > ---
> > hw/s390x/s390-virtio-ccw.c | 16 ++++++++++++----
> > 1 file changed, 12 insertions(+), 4 deletions(-)
Acked-by: Eric Farman <farman@linux.ibm.com>
(I see a v2 is coming for the ioeventfd side, but I was going through
this series today and thought that would affect the next patch rather
than this one.)
next prev parent reply other threads:[~2024-03-11 16:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 19:46 [PATCH v1 0/8] virtio,vhost: Add VIRTIO_F_NOTIFICATION_DATA support Jonah Palmer
2024-03-04 19:46 ` [PATCH v1 1/8] virtio/virtio-pci: Handle extra notification data Jonah Palmer
2024-03-05 8:04 ` Eugenio Perez Martin
2024-03-04 19:46 ` [PATCH v1 2/8] virtio-pci: Lock ioeventfd state with VIRTIO_F_NOTIFICATION_DATA Jonah Palmer
2024-03-08 17:00 ` Michael S. Tsirkin
2024-03-08 17:36 ` Eugenio Perez Martin
2024-03-08 17:45 ` Jonah Palmer
2024-03-08 19:19 ` Michael S. Tsirkin
2024-03-11 14:53 ` Jonah Palmer
2024-03-11 15:47 ` Michael S. Tsirkin
2024-03-12 14:33 ` Jonah Palmer
2024-03-12 14:58 ` Michael S. Tsirkin
2024-03-12 15:06 ` Jonah Palmer
2024-03-04 19:46 ` [PATCH v1 3/8] virtio-mmio: Handle extra notification data Jonah Palmer
2024-03-05 8:05 ` Eugenio Perez Martin
2024-03-04 19:46 ` [PATCH v1 4/8] virtio-mmio: Lock ioeventfd state with VIRTIO_F_NOTIFICATION_DATA Jonah Palmer
2024-03-05 8:05 ` Eugenio Perez Martin
2024-03-04 19:46 ` [PATCH v1 5/8] virtio-ccw: Handle extra notification data Jonah Palmer
2024-03-11 15:55 ` Eric Farman [this message]
2024-03-04 19:46 ` [PATCH v1 6/8] virtio-ccw: Lock ioeventfd state with VIRTIO_F_NOTIFICATION_DATA Jonah Palmer
2024-03-04 19:46 ` [PATCH v1 7/8] vhost/vhost-user: Add VIRTIO_F_NOTIFICATION_DATA to vhost feature bits Jonah Palmer
2024-03-04 19:46 ` [PATCH v1 8/8] virtio: Add VIRTIO_F_NOTIFICATION_DATA property definition Jonah Palmer
2024-03-06 5:33 ` [PATCH v1 0/8] virtio, vhost: Add VIRTIO_F_NOTIFICATION_DATA support Jason Wang
2024-03-06 7:07 ` Eugenio Perez Martin
2024-03-06 7:33 ` [PATCH v1 0/8] virtio,vhost: " Michael S. Tsirkin
2024-03-07 11:16 ` [PATCH v1 0/8] virtio, vhost: " Eugenio Perez Martin
2024-03-08 13:28 ` Lei Yang
2024-03-08 13:39 ` 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=fc53c5567644a8fdd7ca06c89a20b7c52ddb574e.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eperezma@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=iii@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=jonah.palmer@oracle.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=raphael@enfabrica.net \
--cc=richard.henderson@linaro.org \
--cc=si-wei.liu@oracle.com \
--cc=stefanha@redhat.com \
--cc=thuth@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).