diff options
author | Eric Blake | 2020-04-28 22:29:03 +0200 |
---|---|---|
committer | Kevin Wolf | 2020-05-08 13:26:35 +0200 |
commit | bda4cdcbb997d34762e2af27e1f475357a9b4453 (patch) | |
tree | b594654388c54a5d67dd58686702cbd5e8be6246 /backends/hostmem.c | |
parent | ssh: Support BDRV_REQ_ZERO_WRITE for truncate (diff) | |
download | qemu-bda4cdcbb997d34762e2af27e1f475357a9b4453.tar.gz qemu-bda4cdcbb997d34762e2af27e1f475357a9b4453.tar.xz qemu-bda4cdcbb997d34762e2af27e1f475357a9b4453.zip |
parallels: Rework truncation logic
The parallels driver tries to use truncation for image growth, but can
only do so when reads are guaranteed as zero. Now that we have a way
to request zero contents from truncation, we can defer the decision to
actual allocation attempts rather than up front, reducing the number
of places that still use bdrv_has_zero_init_truncate.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20200428202905.770727-8-eblake@redhat.com>
Reviewed-by: Denis V. Lunev <den@openvz.org>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'backends/hostmem.c')
0 files changed, 0 insertions, 0 deletions