diff options
author | Max Reitz | 2014-10-24 15:57:34 +0200 |
---|---|---|
committer | Stefan Hajnoczi | 2014-11-03 12:41:48 +0100 |
commit | ef6dbf1e46ebd1d41ab669df5bba0bbdec6bd374 (patch) | |
tree | b41e965b2dc886f42c9076fb8369402287c5134d /qapi | |
parent | blockjob: Introduce block_job_complete_sync() (diff) | |
download | qemu-ef6dbf1e46ebd1d41ab669df5bba0bbdec6bd374.tar.gz qemu-ef6dbf1e46ebd1d41ab669df5bba0bbdec6bd374.tar.xz qemu-ef6dbf1e46ebd1d41ab669df5bba0bbdec6bd374.zip |
blockjob: Add "ready" field
When a block job signals readiness, this is currently reported only
through QMP. If qemu wants to use block jobs for internal tasks, there
needs to be another way to correctly detect when a block job may be
completed.
For this reason, introduce a bool "ready" which is set when the block
job may be completed.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-id: 1414159063-25977-6-git-send-email-mreitz@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'qapi')
-rw-r--r-- | qapi/block-core.json | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qapi/block-core.json b/qapi/block-core.json index 8f7089e054..77a0cfbd82 100644 --- a/qapi/block-core.json +++ b/qapi/block-core.json @@ -514,12 +514,14 @@ # # @io-status: the status of the job (since 1.3) # +# @ready: true if the job may be completed (since 2.2) +# # Since: 1.1 ## { 'type': 'BlockJobInfo', 'data': {'type': 'str', 'device': 'str', 'len': 'int', 'offset': 'int', 'busy': 'bool', 'paused': 'bool', 'speed': 'int', - 'io-status': 'BlockDeviceIoStatus'} } + 'io-status': 'BlockDeviceIoStatus', 'ready': 'bool'} } ## # @query-block-jobs: |