aboutsummaryrefslogtreecommitdiff
path: root/hw/s390-virtio-bus.h
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2010-02-10 23:37:09 +0100
committerAnthony Liguori <aliguori@us.ibm.com>2010-02-10 16:53:25 -0600
commit428c149b0be790b440e1cbee185b152cdb22feec (patch)
treed44fa0cdd84ba5fb9b4ea3c37791846c36d0a811 /hw/s390-virtio-bus.h
parent37d5ddd6f4a898134b6430c0126378baf5abff4b (diff)
downloadqemu-428c149b0be790b440e1cbee185b152cdb22feec.zip
qemu-428c149b0be790b440e1cbee185b152cdb22feec.tar.gz
qemu-428c149b0be790b440e1cbee185b152cdb22feec.tar.bz2
block: add topology qdev properties
Add three new qdev properties to export block topology information to the guest. This is needed to get optimal I/O alignment for RAID arrays or SSDs. The options are: - physical_block_size to specify the physical block size of the device, this is going to increase from 512 bytes to 4096 kilobytes for many modern storage devices - min_io_size to specify the minimal I/O size without performance impact, this is typically set to the RAID chunk size for arrays. - opt_io_size to specify the optimal sustained I/O size, this is typically the RAID stripe width for arrays. I decided to not auto-probe these values from blkid which might easily be possible as I don't know how to deal with these issues on migration. Note that we specificly only set the physical_block_size, and not the logial one which is the unit all I/O is described in. The reason for that is that IDE does not support increasing the logical block size and at last for now I want to stick to one meachnisms in queue and allow for easy switching of transports for a given backing image which would not be possible if scsi and virtio use real 4k sectors, while ide only uses the physical block exponent. To make this more common for the different block drivers introduce a new BlockConf structure holding all common block properties and a DEFINE_BLOCK_PROPERTIES macro to add them all together, mirroring what is done for network drivers. Also switch over all block drivers to use it, except for the floppy driver which has weird driveA/driveB properties and probably won't require any advanced block options ever. Example usage for a virtio device with 4k physical block size and 8k optimal I/O size: -drive file=scratch.img,media=disk,cache=none,id=scratch \ -device virtio-blk-pci,drive=scratch,physical_block_size=4096,opt_io_size=8192 aliguori: updated patch to take into account BLOCK events Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/s390-virtio-bus.h')
-rw-r--r--hw/s390-virtio-bus.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/s390-virtio-bus.h b/hw/s390-virtio-bus.h
index 8e4763a..0ea8f54 100644
--- a/hw/s390-virtio-bus.h
+++ b/hw/s390-virtio-bus.h
@@ -38,7 +38,7 @@ typedef struct VirtIOS390Device {
ram_addr_t feat_offs;
uint8_t feat_len;
VirtIODevice *vdev;
- DriveInfo *dinfo;
+ BlockConf block;
NICConf nic;
uint32_t host_features;
/* Max. number of ports we can have for a the virtio-serial device */