| commit | 63d5341f8553ff78ae99407ff8ad5a6648b95a30 | |
| author | zhenwei pi <pizhenwei@bytedance.com> | |
| Mon, 5 Nov 2018 03:04:56 +0000 (5 11:04 +0800) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Mon, 12 Nov 2018 16:46:57 +0000 (12 17:46 +0100) | ||
| tree | ccd824123bd654a2d1ec9097373d9f463d20a016 | treesnapshot (tar.gz zip) |
| parent | db0754df88e3ca4797539c1edbde596d871b64b6 | commitdiff |
blockdev: handle error on block latency histogram set error
Function block_latency_histogram_set may return error, but qapi ignore this.
This can be reproduced easily by qmp command:
virsh qemu-monitor-command INSTANCE '{"execute":"x-block-latency-histogram-set",
"arguments":{"device":"drive-virtio-disk1","boundaries":[10,200,40]}}'
In fact this command does not work, but we still get success result.
qmp_x_block_latency_histogram_set is a batch setting API, report error ASAP.
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Function block_latency_histogram_set may return error, but qapi ignore this.
This can be reproduced easily by qmp command:
virsh qemu-monitor-command INSTANCE '{"execute":"x-block-latency-histogram-set",
"arguments":{"device":"drive-virtio-disk1","boundaries":[10,200,40]}}'
In fact this command does not work, but we still get success result.
qmp_x_block_latency_histogram_set is a batch setting API, report error ASAP.
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| blockdev.c | diffblobblamehistory |