summaryrefslogtreecommitdiffstats
path: root/hw/arm/microbit.c
diff options
context:
space:
mode:
authorVladimir Sementsov-Ogievskiy2020-12-11 19:39:34 +0100
committerEric Blake2021-02-03 15:17:12 +0100
commita5215b8fdf1f8b284b4e5ba4895a4b091b503444 (patch)
tree8c3478c0c9cee42ef3e3c67098067b5cc9093fc5 /hw/arm/microbit.c
parentblock/io: support int64_t bytes in read/write wrappers (diff)
downloadqemu-a5215b8fdf1f8b284b4e5ba4895a4b091b503444.tar.gz
qemu-a5215b8fdf1f8b284b4e5ba4895a4b091b503444.tar.xz
qemu-a5215b8fdf1f8b284b4e5ba4895a4b091b503444.zip
block/io: use int64_t bytes in copy_range
We are generally moving to int64_t for both offset and bytes parameters on all io paths. Main motivation is realization of 64-bit write_zeroes operation for fast zeroing large disk chunks, up to the whole disk. We chose signed type, to be consistent with off_t (which is signed) and with possibility for signed return type (where negative value means error). So, convert now copy_range parameters which are already 64bit to signed type. It's safe as we don't work with requests overflowing BDRV_MAX_LENGTH (which is less than INT64_MAX), and do check the requests in bdrv_co_copy_range_internal() (by bdrv_check_request32(), which calls bdrv_check_request()). Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Message-Id: <20201211183934.169161-17-vsementsov@virtuozzo.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'hw/arm/microbit.c')
0 files changed, 0 insertions, 0 deletions