From: Coiby Xu <coiby.xu@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, bharatlkmlkvm@gmail.com,
Coiby Xu <coiby.xu@gmail.com>,
stefanha@redhat.com
Subject: [PATCH v1 0/5] vhost-user block device backend implementation
Date: Mon, 13 Jan 2020 12:56:59 +0800 [thread overview]
Message-ID: <20200113045704.12318-1-coiby.xu@gmail.com> (raw)
This patch series is an implementation of vhost-user-backend server, thanks to Stefan's guidance after reviewing the draft version and the instructions on https://wiki.qemu.org/Google_Summer_of_Code_2019#vhost-user-blk_device_backend,
Vhost-user-backend server is a UserCreatable object and can be started using object_add,
(qemu) object_add vhost-user-server,id=ID,unix_socket=/tmp/vhost-user-blk_vhost.socket,name=DRIVE_NAME,writable=off
(qemu) object_del ID
or appending the "-object" option when starting QEMU,
$ -object vhost-user-server,id=disk,unix_socket=/tmp/vhost-user-blk_vhost.socket,name=disk,writable=off
Then vhost-user client can connect to the server backend. For example, QEMU could act as a client,
$ -m 256 -object memory-backend-memfd,id=mem,size=256M,share=on -numa node,memdev=mem -chardev socket,id=char1,path=/tmp/vhost-user-blk_vhost.socket -device vhost-user-blk-pci,id=blk0,chardev=char1
And guest OS could access this vhost-user block device after mouting it.
patches are against commit 035eed4c0d257c905a556fa0f4865a0c077b4e7f.
Coiby Xu (5):
vhost-user block device backend
extend libvhost to support IOThread
a standone-alone tool to directly share disk image file via vhost-user
protocol
new qTest case for the vhost-user-blk device backend
building configuration files changes
Makefile | 1 +
Makefile.objs | 2 +-
Makefile.target | 1 +
blockdev-vu.c | 1008 +++++++++++++++++++++++++
configure | 2 +-
contrib/libvhost-user/libvhost-user.c | 64 +-
contrib/libvhost-user/libvhost-user.h | 36 +-
include/block/vhost-user.h | 46 ++
qemu-vu.c | 264 +++++++
tests/Makefile.include | 5 +-
tests/libqos/vhost-user-blk.c | 125 +++
tests/libqos/vhost-user-blk.h | 44 ++
tests/vhost-user-blk-test.c | 691 +++++++++++++++++
vl.c | 4 +
14 files changed, 2277 insertions(+), 16 deletions(-)
create mode 100644 blockdev-vu.c
create mode 100644 include/block/vhost-user.h
create mode 100644 qemu-vu.c
create mode 100644 tests/libqos/vhost-user-blk.c
create mode 100644 tests/libqos/vhost-user-blk.h
create mode 100644 tests/vhost-user-blk-test.c
--
2.24.1
next reply other threads:[~2020-01-13 4:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 4:56 Coiby Xu [this message]
2020-01-13 4:57 ` [PATCH v1 1/5] vhost-user block device backend Coiby Xu
2020-01-13 4:57 ` [PATCH v1 2/5] extend libvhost to support IOThread Coiby Xu
2020-01-13 4:57 ` [PATCH v1 3/5] a standone-alone tool to directly share disk image file via vhost-user protocol Coiby Xu
2020-01-13 4:57 ` [PATCH v1 4/5] new qTest case for the vhost-user-blk device backend Coiby Xu
2020-01-13 4:57 ` [PATCH v1 5/5] building configuration files changes Coiby Xu
2020-01-13 5:21 ` [PATCH v1 0/5] vhost-user block device backend implementation no-reply
2020-01-14 14:11 ` Coiby Xu
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=20200113045704.12318-1-coiby.xu@gmail.com \
--to=coiby.xu@gmail.com \
--cc=bharatlkmlkvm@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).