summaryrefslogtreecommitdiffstats
path: root/libdecnumber
diff options
context:
space:
mode:
authorVladimir Sementsov-Ogievskiy2020-12-11 19:39:33 +0100
committerEric Blake2021-02-03 15:17:12 +0100
commite9e52efdc53bf7746bdb3c21f1a9ee5da298c6a2 (patch)
treef6c1747591b07eb37000d5228088c5b02ce21507 /libdecnumber
parentblock/io: support int64_t bytes in bdrv_co_p{read,write}v_part() (diff)
downloadqemu-e9e52efdc53bf7746bdb3c21f1a9ee5da298c6a2.tar.gz
qemu-e9e52efdc53bf7746bdb3c21f1a9ee5da298c6a2.tar.xz
qemu-e9e52efdc53bf7746bdb3c21f1a9ee5da298c6a2.zip
block/io: support int64_t bytes in read/write wrappers
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). Now, since bdrv_co_preadv_part() and bdrv_co_pwritev_part() have been updated, update all their wrappers. For all of them type of 'bytes' is widening, so callers are safe. We have update request_fn in blkverify.c simultaneously. Still it's just a pointer to one of bdrv_co_pwritev() or bdrv_co_preadv(), and type is widening for callers of the request_fn anyway. Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Message-Id: <20201211183934.169161-16-vsementsov@virtuozzo.com> Reviewed-by: Eric Blake <eblake@redhat.com> [eblake: grammar tweak] Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'libdecnumber')
0 files changed, 0 insertions, 0 deletions