From: Marc Hartmayer <mhartmay@linux.ibm.com>
To: <qemu-devel@nongnu.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [RFC v2 0/3] Enable virtio-fs on s390x
Date: Fri, 17 Jul 2020 11:29:26 +0200 [thread overview]
Message-ID: <20200717092929.19453-1-mhartmay@linux.ibm.com> (raw)
This RFC is about enabling virtio-fs on s390x. For that we need
+ some shim code (first patch), and we need
+ libvhost-user to deal with virtio endiannes for non-legacy virtio
devices as mandated by the spec.
libvhost-access.h is based on hw/virtio/virtio-access.h.
How to use?
For general instructions how to use virtio-fs (on x86) please have a
look at https://virtio-fs.gitlab.io/howto-qemu.html. Most of the
instructions can also be applied on s390x.
In short:
1. Install self-compiled QEMU with this patch series applied
2. Prepare host and guest kernel so they support virtio-fs
Start virtiofsd on the host
$ virtiofsd -f --socket-path=/tmp/vhostqemu -o source=/tmp/shared
Now you can start QEMU in a separate shell on the host:
$ qemu-system-s390x -machine type=s390-ccw-virtio,accel=kvm,memory-backend=mem \
-object memory-backend-file,id=mem,size=2G,mem-path=/dev/shm/virtiofs,share=on,prealloc=on,prealloc-threads=1 \
-chardev socket,id=char0,path=/tmp/vhostqemu -device vhost-user-fs-ccw,queue-size=1024,chardev=char0,tag=myfs \
-drive if=virtio,file=disk.qcow2 \
-m 2G -smp 2 -nographic
Log into the guest and mount it
$ mount -t virtiofs myfs /mnt
Changelog:
v1->v2:
+ rebased
+ drop patch "libvhost-user: print invalid address on vu_panic" as it's not related to this series
+ drop patch "[RFC 4/4] HACK: Hard-code the libvhost-user.o-cflags for s390x"
+ patch "virtio: add vhost-user-fs-ccw device": replace qdev_set_parent_bus and object_property_set_bool by qdev_realize
+ patch "libvhost-user: handle endianness as mandated by the spec":
Drop support for legacy virtio devices
+ add patch to fence legacy virtio devices
Halil Pasic (1):
virtio: add vhost-user-fs-ccw device
Marc Hartmayer (2):
libvhost-user: handle endianness as mandated by the spec
libvhost-user: fence legacy virtio devices
contrib/libvhost-user/libvhost-access.h | 71 ++++++++++++++
contrib/libvhost-user/libvhost-user.c | 125 +++++++++++++-----------
hw/s390x/Makefile.objs | 1 +
hw/s390x/vhost-user-fs-ccw.c | 73 ++++++++++++++
4 files changed, 211 insertions(+), 59 deletions(-)
create mode 100644 contrib/libvhost-user/libvhost-access.h
create mode 100644 hw/s390x/vhost-user-fs-ccw.c
--
2.25.4
next reply other threads:[~2020-07-17 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:29 Marc Hartmayer [this message]
2020-07-17 9:29 ` [RFC v2 1/3] virtio: add vhost-user-fs-ccw device Marc Hartmayer
2020-07-21 13:47 ` Stefan Hajnoczi
2020-07-28 10:31 ` Cornelia Huck
2020-07-28 11:25 ` Halil Pasic
2020-07-28 11:33 ` Cornelia Huck
2020-07-17 9:29 ` [RFC v2 2/3] libvhost-user: handle endianness as mandated by the spec Marc Hartmayer
2020-07-21 12:48 ` Stefan Hajnoczi
2020-07-30 13:15 ` Marc Hartmayer
2020-07-21 13:40 ` Michael S. Tsirkin
2020-07-21 16:44 ` Halil Pasic
2020-07-28 10:48 ` Cornelia Huck
2020-07-28 11:31 ` Halil Pasic
2020-07-28 10:52 ` Marc Hartmayer
2020-07-29 14:13 ` Michael S. Tsirkin
2020-07-29 16:11 ` Marc Hartmayer
2020-07-17 9:29 ` [RFC v2 3/3] libvhost-user: fence legacy virtio devices Marc Hartmayer
2020-07-21 13:47 ` Stefan Hajnoczi
2020-07-17 10:26 ` [RFC v2 0/3] Enable virtio-fs on s390x no-reply
2020-07-17 10:31 ` no-reply
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=20200717092929.19453-1-mhartmay@linux.ibm.com \
--to=mhartmay@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.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).