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. Changes v1->v2: * move the 'is guest provided queue size too large?' check from virtio-mmio into the core virtio 'set_num' function * rebase (including adding owner parameter to memory region init call in virtio-mmio.c) Changes v2->v3: * drop the overcomplicated error return encoding from qemu_devtree_setprop_sized_cells() and just catch "user specified ram size too big for dtb" in boot.c 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 | 33 ++++ hw/arm/boot.c | 34 ++-- hw/arm/vexpress.c | 128 ++++++++++-- hw/virtio/Makefile.objs | 1 + hw/virtio/virtio-mmio.c | 421 ++++++++++++++++++++++++++++++++++++++++ hw/virtio/virtio.c | 40 +++- include/hw/arm/arm.h | 4 + include/hw/virtio/virtio-bus.h | 6 + include/hw/virtio/virtio.h | 2 + include/sysemu/device_tree.h | 59 ++++++ 10 files changed, 689 insertions(+), 39 deletions(-) create mode 100644 hw/virtio/virtio-mmio.c -- 1.7.9.5 _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
