From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
patches@linaro.org, Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>,
kvmarm@lists.cs.columbia.edu,
KONRAD Frederic <fred.konrad@greensocs.com>
Subject: [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress
Date: Thu, 27 Jun 2013 14:04:07 +0100 [thread overview]
Message-ID: <1372338255-3934-1-git-send-email-peter.maydell@linaro.org> (raw)
This patch series adds an implementation of the virtio-mmio
transport, and uses it in the vexpress-a9 and vexpress-a15
board models.
The basic idea is that the board instantiates some transports,
the user can create backends which automatically plug into them
(via -device virtio-blk-backend and the like), and we tell the
guest kernel about them using a new arm/boot hook that lets
the board modify the user's device tree blob.
(The last part of this represents another reluctant step into
manipulating device trees; however interrupt-controller and
virtio nodes should be sufficiently stable to be safe as these
things go.)
Is there a convenient way to say "don't create the transport
if there's no backend to plug into it"?
Sample command line:
./build/x86/arm-softmmu/qemu-system-arm -machine type=vexpress-a15 \
-serial stdio -display none -kernel zImage \
-dtb vexpress-v2p-ca15-tc1.dtb \
-append "root=/dev/mmcblk0 rw console=ttyAMA0 rootwait earlyprintk" \
-sd arm-wheezy.img -device virtio-serial-device \
-drive if=none,file=debian_lenny_arm_small.qcow2,id=foo \
-device virtio-blk-device,drive=foo
(note that '-device virtio-blk' and '-drive if=virtio' won't
work since they will result in the creation of PCI virtio devices.)
The first two patches here are effectively a 'v2' of the versions
I sent out earlier this week; I've updated them as per review so
they no longer have the awkward "varargs don't promote" problem.
The core virtio patches are based initially on the prototype
versions I wrote back in 2011, which Fred Konrad has subsequently
updated to work on top of his virtio refactoring. I then did some
minor fixes and cleanup.
When I get mach-virt into shape that will use virtio-mmio too.
Peter Maydell (8):
device_tree: Add qemu_devtree_setprop_sized_cells() utility functions
arm/boot: Use qemu_devtree_setprop_sized_cells()
virtio: Add support for guest setting of queue size
virtio: Support transports which can specify the vring alignment
virtio: Implement MMIO based virtio transport
arm/boot: Allow boards to modify the FDT blob
vexpress: Make VEDBoardInfo extend arm_boot_info
vexpress: Add virtio-mmio transports
device_tree.c | 31 +++
hw/arm/boot.c | 33 ++--
hw/arm/vexpress.c | 128 ++++++++++--
hw/virtio/Makefile.objs | 1 +
hw/virtio/virtio-mmio.c | 424 ++++++++++++++++++++++++++++++++++++++++
hw/virtio/virtio.c | 38 +++-
include/hw/arm/arm.h | 4 +
include/hw/virtio/virtio-bus.h | 6 +
include/hw/virtio/virtio.h | 2 +
include/sysemu/device_tree.h | 62 ++++++
10 files changed, 690 insertions(+), 39 deletions(-)
create mode 100644 hw/virtio/virtio-mmio.c
--
1.7.9.5
next reply other threads:[~2013-06-27 13:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 13:04 Peter Maydell [this message]
2013-06-27 13:04 ` [Qemu-devel] [PATCH 1/8] device_tree: Add qemu_devtree_setprop_sized_cells() utility functions Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 2/8] arm/boot: Use qemu_devtree_setprop_sized_cells() Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 3/8] virtio: Add support for guest setting of queue size Peter Maydell
2013-07-08 19:39 ` Anthony Liguori
2013-07-09 8:27 ` Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 4/8] virtio: Support transports which can specify the vring alignment Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 5/8] virtio: Implement MMIO based virtio transport Peter Maydell
2013-07-08 19:52 ` Anthony Liguori
2013-06-27 13:04 ` [Qemu-devel] [PATCH 6/8] arm/boot: Allow boards to modify the FDT blob Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 7/8] vexpress: Make VEDBoardInfo extend arm_boot_info Peter Maydell
2013-06-27 13:04 ` [Qemu-devel] [PATCH 8/8] vexpress: Add virtio-mmio transports Peter Maydell
2013-07-08 12:57 ` [Qemu-devel] [PATCH 0/8] Add virtio-mmio and use it in vexpress Alexander Graf
2013-07-08 12:59 ` Alexander Graf
2013-07-08 13:08 ` Peter Maydell
2013-07-08 13:16 ` Alexander Graf
2013-07-08 13:23 ` Peter Maydell
2013-07-08 13:45 ` Alexander Graf
2013-07-08 14:06 ` Peter Maydell
2013-07-08 20:08 ` Anthony Liguori
2013-07-08 20:47 ` Alexander Graf
2013-07-08 21:06 ` Anthony Liguori
2013-07-09 9:28 ` Andreas Färber
2013-07-10 10:56 ` Alexander Graf
2013-07-17 9:30 ` Christoffer Dall
2013-07-17 9:34 ` Peter Maydell
2013-07-17 12:41 ` Anthony Liguori
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=1372338255-3934-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=fred.konrad@greensocs.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).