The blk_get_max_hw_transfer API was recently added in 6.1.0. It allows querying an underlying block device its max transfer capability. This commit changes virtio-blk to use this.
Signed-off-by: Or Ozeri <o...@il.ibm.com> --- hw/block/virtio-blk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c index f139cd7cc9..1ba9a06888 100644 --- a/hw/block/virtio-blk.c +++ b/hw/block/virtio-blk.c @@ -458,7 +458,7 @@ static void virtio_blk_submit_multireq(BlockBackend *blk, MultiReqBuffer *mrb) return; } - max_transfer = blk_get_max_transfer(mrb->reqs[0]->dev->blk); + max_transfer = blk_get_max_hw_transfer(mrb->reqs[0]->dev->blk); qsort(mrb->reqs, mrb->num_reqs, sizeof(*mrb->reqs), &multireq_compare); -- 2.25.1