From: Alvaro Karsz <alvaro.karsz@solid-run.com>
To: mst@redhat.com, jasowang@redhat.com
Cc: virtualization@lists.linux-foundation.org, cohuck@redhat.com,
pasic@linux.ibm.com, farman@linux.ibm.com,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, yan@daynix.com, viktor@daynix.com,
Alvaro Karsz <alvaro.karsz@solid-run.com>
Subject: [PATCH 0/2] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
Date: Thu, 13 Apr 2023 11:18:53 +0300 [thread overview]
Message-ID: <20230413081855.36643-1-alvaro.karsz@solid-run.com> (raw)
Add VIRTIO_F_NOTIFICATION_DATA feature support for the MMIO, channel
I/O, modern PCI and vDPA transports.
This patchset binds 2 patches that were sent separately to the mailing
lists.
The first one [1] adds support for the MMIO, channel I/O and modern PCI transports.
The second one [2] adds support to the vDPA transport.
[1] https://lore.kernel.org/lkml/20230324195029.2410503-1-viktor@daynix.com/
[2] https://lore.kernel.org/virtualization/20230409070706.3288876-1-alvaro.karsz@solid-run.com/
Alvaro Karsz (1):
virtio-vdpa: add VIRTIO_F_NOTIFICATION_DATA feature support
Viktor Prutyanov (1):
virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
drivers/s390/virtio/virtio_ccw.c | 22 +++++++++++++++++++---
drivers/virtio/virtio_mmio.c | 18 +++++++++++++++++-
drivers/virtio/virtio_pci_modern.c | 17 ++++++++++++++++-
drivers/virtio/virtio_ring.c | 19 +++++++++++++++++++
drivers/virtio/virtio_vdpa.c | 23 +++++++++++++++++++++--
include/linux/vdpa.h | 9 +++++++++
include/linux/virtio_ring.h | 2 ++
include/uapi/linux/virtio_config.h | 6 ++++++
8 files changed, 109 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-13 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 8:18 Alvaro Karsz [this message]
2023-04-13 8:18 ` [PATCH 1/2] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support Alvaro Karsz
2023-04-13 8:18 ` [PATCH 2/2] virtio-vdpa: " Alvaro Karsz
2023-04-17 8:05 ` 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=20230413081855.36643-1-alvaro.karsz@solid-run.com \
--to=alvaro.karsz@solid-run.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=viktor@daynix.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yan@daynix.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