aboutsummaryrefslogtreecommitdiff
path: root/block_int.h
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2010-07-28 11:26:29 +0200
committerKevin Wolf <kwolf@redhat.com>2010-08-03 15:57:22 +0200
commit336c1c12551ff0a6e1a2af226d6cbdbadd2e02b5 (patch)
tree0f5945db7be86283562c5d86abf3eb36cb4d695c /block_int.h
parentbd0858bb460c0c134e9a62c73e60e465037b1240 (diff)
downloadqemu-336c1c12551ff0a6e1a2af226d6cbdbadd2e02b5.zip
qemu-336c1c12551ff0a6e1a2af226d6cbdbadd2e02b5.tar.gz
qemu-336c1c12551ff0a6e1a2af226d6cbdbadd2e02b5.tar.bz2
block: Fix bdrv_has_zero_init
Assuming that any image on a block device is not properly zero-initialized is actually wrong: Only raw images have this problem. Any other image format shouldn't care about it, they initialize everything properly themselves. Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block_int.h')
-rw-r--r--block_int.h7
1 files changed, 5 insertions, 2 deletions
diff --git a/block_int.h b/block_int.h
index f075a8c..7d5e751 100644
--- a/block_int.h
+++ b/block_int.h
@@ -127,8 +127,11 @@ struct BlockDriver {
void (*bdrv_debug_event)(BlockDriverState *bs, BlkDebugEvent event);
- /* Set if newly created images are not guaranteed to contain only zeros */
- int no_zero_init;
+ /*
+ * Returns 1 if newly created images are guaranteed to contain only
+ * zeros, 0 otherwise.
+ */
+ int (*bdrv_has_zero_init)(BlockDriverState *bs);
QLIST_ENTRY(BlockDriver) list;
};