From: Xie Yongji <xieyongji@bytedance.com>
To: mst@redhat.com, stefanha@redhat.com, sgarzare@redhat.com,
raphael.norwitz@nutanix.com, lingshan.zhu@intel.com,
changpeng.liu@intel.com, jasowang@redhat.com, kwolf@redhat.com,
mreitz@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [PATCH 0/3] Introduce vhost-vdpa block device
Date: Thu, 8 Apr 2021 18:12:49 +0800 [thread overview]
Message-ID: <20210408101252.552-1-xieyongji@bytedance.com> (raw)
Since we already have some ways to emulate vDPA block device
in kernel[1] or userspace[2]. This series tries to introduce a
new vhost-vdpa block device for that. To use it, we can add
something like:
qemu-system-x86_64 \
-device vhost-vdpa-blk-pci,vdpa-dev=/dev/vhost-vdpa-0
You can also get the code and kernel changes from below repositories:
https://github.com/bytedance/qemu/tree/vhost-vdpa-blk
https://github.com/bytedance/linux/tree/vhost-vdpa-blk
Thank you!
[1] https://lore.kernel.org/kvm/20210315163450.254396-1-sgarzare@redhat.com/
[2] https://lore.kernel.org/kvm/20210331080519.172-1-xieyongji@bytedance.com/
Xie Yongji (3):
Remove redundant declaration of address_space_memory
vhost-blk: add vhost-blk-common abstraction
vhost-vdpa-blk: Introduce vhost-vdpa-blk host device
hw/block/Kconfig | 5 +
hw/block/meson.build | 3 +-
hw/block/vhost-blk-common.c | 291 +++++++++++++++++++++++++
hw/block/vhost-user-blk.c | 306 +++++----------------------
hw/block/vhost-vdpa-blk.c | 227 ++++++++++++++++++++
hw/virtio/meson.build | 1 +
hw/virtio/vhost-user-blk-pci.c | 7 +-
hw/virtio/vhost-vdpa-blk-pci.c | 101 +++++++++
hw/virtio/vhost-vdpa.c | 1 +
include/hw/virtio/vhost-blk-common.h | 50 +++++
include/hw/virtio/vhost-user-blk.h | 20 +-
include/hw/virtio/vhost-vdpa-blk.h | 30 +++
include/hw/virtio/vhost-vdpa.h | 1 -
13 files changed, 762 insertions(+), 281 deletions(-)
create mode 100644 hw/block/vhost-blk-common.c
create mode 100644 hw/block/vhost-vdpa-blk.c
create mode 100644 hw/virtio/vhost-vdpa-blk-pci.c
create mode 100644 include/hw/virtio/vhost-blk-common.h
create mode 100644 include/hw/virtio/vhost-vdpa-blk.h
--
2.25.1
next reply other threads:[~2021-04-08 10:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 10:12 Xie Yongji [this message]
2021-04-08 10:12 ` [PATCH 1/3] vhost-vdpa: Remove redundant declaration of address_space_memory Xie Yongji
2021-04-08 10:19 ` Philippe Mathieu-Daudé
2021-04-08 10:12 ` [PATCH 2/3] vhost-blk: Add vhost-blk-common abstraction Xie Yongji
2021-04-08 23:21 ` Raphael Norwitz
2021-04-09 2:38 ` Yongji Xie
2021-04-26 14:49 ` Stefan Hajnoczi
2021-04-27 10:26 ` Yongji Xie
2021-04-08 10:12 ` [PATCH 3/3] vhost-vdpa-blk: Introduce vhost-vdpa-blk host device Xie Yongji
2021-04-09 6:02 ` Jason Wang
2021-04-09 8:17 ` Yongji Xie
2021-04-12 7:14 ` Jason Wang
2021-04-12 7:51 ` Yongji Xie
2021-04-26 15:05 ` Stefan Hajnoczi
2021-04-27 10:33 ` Yongji Xie
2021-04-26 15:33 ` [PATCH 0/3] Introduce vhost-vdpa block device Stefan Hajnoczi
2021-04-27 10:24 ` Yongji Xie
2021-04-27 14:28 ` Stefan Hajnoczi
2021-04-28 11:27 ` Yongji Xie
2021-04-28 12:21 ` Stefano Garzarella
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=20210408101252.552-1-xieyongji@bytedance.com \
--to=xieyongji@bytedance.com \
--cc=changpeng.liu@intel.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.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).