From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: liang yan <lyan@suse.com>,
Jailhouse <jailhouse-dev@googlegroups.com>,
Claudio Fontana <claudio.fontana@gmail.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [RFC][PATCH 0/3] IVSHMEM version 2 device for QEMU
Date: Mon, 11 Nov 2019 13:57:09 +0100 [thread overview]
Message-ID: <cover.1573477032.git.jan.kiszka@siemens.com> (raw)
To get the ball rolling after my presentation of the topic at KVM Forum
[1] and many fruitful discussions around it, this is a first concrete
code series. As discussed, I'm starting with the IVSHMEM implementation
of a QEMU device and server. It's RFC because, besides specification and
implementation details, there will still be some decisions needed about
how to integrate the new version best into the existing code bases.
If you want to play with this, the basic setup of the shared memory
device is described in patch 1 and 3. UIO driver and also the
virtio-ivshmem prototype can be found at
http://git.kiszka.org/?p=linux.git;a=shortlog;h=refs/heads/queues/ivshmem2
Accessing the device via UIO is trivial enough. If you want to use it
for virtio, this is additionally to the description in patch 3 needed on
the virtio console backend side:
modprobe uio_ivshmem
echo "1af4 1110 1af4 1100 ffc003 ffffff" > /sys/bus/pci/drivers/uio_ivshmem/new_id
linux/tools/virtio/virtio-ivshmem-console /dev/uio0
And for virtio block:
echo "1af4 1110 1af4 1100 ffc002 ffffff" > /sys/bus/pci/drivers/uio_ivshmem/new_id
linux/tools/virtio/virtio-ivshmem-console /dev/uio0 /path/to/disk.img
After that, you can start the QEMU frontend instance with the
virtio-ivshmem driver installed which can use the new /dev/hvc* or
/dev/vda* as usual.
Any feedback welcome!
Jan
PS: Let me know if I missed someone potentially interested in this topic
on CC - or if you would like to be dropped from the list.
PPS: The Jailhouse queues are currently out of sync /wrt minor details
of this one, primarily the device ID. Will update them when the general
direction is clear.
[1] https://kvmforum2019.sched.com/event/TmxI
Jan Kiszka (3):
hw/misc: Add implementation of ivshmem revision 2 device
docs/specs: Add specification of ivshmem device revision 2
contrib: Add server for ivshmem revision 2
Makefile | 3 +
Makefile.objs | 1 +
configure | 1 +
contrib/ivshmem2-server/Makefile.objs | 1 +
contrib/ivshmem2-server/ivshmem2-server.c | 462 ++++++++++++
contrib/ivshmem2-server/ivshmem2-server.h | 158 +++++
contrib/ivshmem2-server/main.c | 313 +++++++++
docs/specs/ivshmem-2-device-spec.md | 333 +++++++++
hw/misc/Makefile.objs | 2 +-
hw/misc/ivshmem2.c | 1091 +++++++++++++++++++++++++++++
include/hw/misc/ivshmem2.h | 48 ++
11 files changed, 2412 insertions(+), 1 deletion(-)
create mode 100644 contrib/ivshmem2-server/Makefile.objs
create mode 100644 contrib/ivshmem2-server/ivshmem2-server.c
create mode 100644 contrib/ivshmem2-server/ivshmem2-server.h
create mode 100644 contrib/ivshmem2-server/main.c
create mode 100644 docs/specs/ivshmem-2-device-spec.md
create mode 100644 hw/misc/ivshmem2.c
create mode 100644 include/hw/misc/ivshmem2.h
--
2.16.4
next reply other threads:[~2019-11-11 13:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 12:57 Jan Kiszka [this message]
2019-11-11 12:57 ` [RFC][PATCH 1/3] hw/misc: Add implementation of ivshmem revision 2 device Jan Kiszka
2019-11-11 12:57 ` [RFC][PATCH 2/3] docs/specs: Add specification of ivshmem device revision 2 Jan Kiszka
2019-11-11 13:45 ` Michael S. Tsirkin
2019-11-11 13:59 ` Jan Kiszka
2019-11-11 15:08 ` Michael S. Tsirkin
2019-11-11 15:27 ` Daniel P. Berrangé
2019-11-11 15:42 ` Jan Kiszka
2019-11-11 16:14 ` Michael S. Tsirkin
2019-11-11 16:25 ` Jan Kiszka
2019-11-11 16:11 ` Michael S. Tsirkin
2019-11-11 16:38 ` Jan Kiszka
2019-11-12 8:04 ` Michael S. Tsirkin
2019-11-20 18:15 ` Jan Kiszka
2019-12-05 11:14 ` Markus Armbruster
2019-12-05 21:29 ` Jan Kiszka
2019-12-06 10:08 ` Markus Armbruster
2019-11-11 12:57 ` [RFC][PATCH 3/3] contrib: Add server for ivshmem " Jan Kiszka
2019-11-12 0:56 ` [RFC][PATCH 0/3] IVSHMEM version 2 device for QEMU no-reply
2019-11-27 15:28 ` Liang Yan
2019-11-27 17:19 ` Jan Kiszka
2019-12-02 6:16 ` Jan Kiszka
[not found] ` <877b0cd9-d1c5-00c9-c4b6-567c67740962@suse.com>
2019-12-03 7:14 ` Jan Kiszka
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=cover.1573477032.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=armbru@redhat.com \
--cc=claudio.fontana@gmail.com \
--cc=hare@suse.de \
--cc=jailhouse-dev@googlegroups.com \
--cc=lyan@suse.com \
--cc=mst@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).