summaryrefslogtreecommitdiff
path: root/tests/qemu-iotests/082.out
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2016-03-03 11:37:48 +0100
committerKevin Wolf <kwolf@redhat.com>2016-03-30 12:16:02 +0200
commitc83f9fba2a4ae3f07a7ac8ff8c021f539a08b6ce (patch)
tree3415e706dcd6ccca77ac108551e139c7c95e067d /tests/qemu-iotests/082.out
parentbfd18d1e0b06608226fcef1982c3a439c49c3366 (diff)
downloadqemu-c83f9fba2a4ae3f07a7ac8ff8c021f539a08b6ce.tar.gz
qemu-c83f9fba2a4ae3f07a7ac8ff8c021f539a08b6ce.tar.bz2
qemu-c83f9fba2a4ae3f07a7ac8ff8c021f539a08b6ce.zip
block/qapi: Use blk_enable_write_cache()
Now that WCE is handled on the BlockBackend level, the flag is meaningless for BDSes. As the schema requires us to fill the field, we return an enabled write cache for them. Note that this means that querying the BlockBackend name may return writethrough as the cache information, whereas querying the node-name of the root of that same BlockBackend will return writeback. This may appear odd at first, but it actually makes sense because it correctly repesents the layer that implements the WCE handling. This becomes more apparent when you consider nodes that are the root node of multiple BlockBackends, where each BB can have its own WCE setting. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/082.out')
0 files changed, 0 insertions, 0 deletions