On Mon, 11 Feb 2013 10:37:20 +0100
address@hidden wrote:
From: KONRAD Frederic <address@hidden>
This is the next part of virtio-refactoring.
I send it now to have it reviewed.
Basically it creates virtio-blk device which extends virtio-device.
Then a virtio-blk can be connected on a virtio-bus.
virtio-blk-pci, virtio-blk-s390x, virtio-blk-ccw are created too, they extend
respectively virtio-pci, virtio-s390-device, virtio-ccw-device and have a
virtio-blk.
It is on top of "virtio: make virtio device's structures public" I posted
before, but you can checkout my branch here:
git://git.greensocs.com/qemu_virtio.git virtio-blk-v4
I made basic tests (with linux guests) on:
* qemu-system-i386
* qemu-system-s390x
I didn't test dataplane as I don't know how it works? Depends on linux AIO?
Stefan can you try launching dataplane with my tree?
I didn't test virtio-ccw as I don't have the hardware.
Anyone can try it on ccw hardware?
Compiles and works for me. My block device shows up in 'info qtree' as
follows:
dev: virtual-css-bridge, id ""
irq 0
bus: virtual-css
type virtual-css-bus
dev: virtio-blk-ccw, id "virtio-disk0"
devno = "fe.0.0815"
drive = drive-virtio-disk0
logical_block_size = 512
physical_block_size = 512
min_io_size = 0
opt_io_size = 0
bootindex = -1
discard_granularity = 0
serial = <null>
scsi = on
indirect_desc = on
event_idx = on
bus: virtio-disk0.0
type virtio-ccw-bus
dev: virtio-blk, id ""
drive = drive-virtio-disk0
logical_block_size = 512
physical_block_size = 512
min_io_size = 0
opt_io_size = 0
bootindex = -1
discard_granularity = 0
cyls = 16383
heads = 16
secs = 63
serial = <null>
config-wce = off
scsi = on