diff options
author | Fam Zheng <famz@redhat.com> | 2014-05-23 21:29:42 +0800 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2014-05-28 14:28:46 +0200 |
commit | fbe40ff780564526e6f639b3b78366727d34955c (patch) | |
tree | 19b5ee9ccafd3ea28bebbf2ff7c44017a6228294 /user-exec.c | |
parent | 8574575f90e73ec93c2ef4bda4ae41c92fc8e644 (diff) | |
download | qemu-fbe40ff780564526e6f639b3b78366727d34955c.tar.gz qemu-fbe40ff780564526e6f639b3b78366727d34955c.tar.bz2 qemu-fbe40ff780564526e6f639b3b78366727d34955c.zip |
block: Introduce op_blockers to BlockDriverState
BlockDriverState.op_blockers is an array of lists with BLOCK_OP_TYPE_MAX
elements. Each list is a list of blockers of an operation type
(BlockOpType), that marks this BDS as currently blocked for a certain
type of operation with reason errors stored in the list. The rule of
usage is:
* BDS user who wants to take an operation should check if there's any
blocker of the type with bdrv_op_is_blocked().
* BDS user who wants to block certain types of operation, should call
bdrv_op_block (or bdrv_op_block_all to block all types of operations,
which is similar to the existing bdrv_set_in_use()).
* A blocker is only referenced by op_blockers, so the lifecycle is
managed by caller, and shouldn't be lost until unblock, so typically
a caller does these:
- Allocate a blocker with error_setg or similar, call bdrv_op_block()
to block some operations.
- Hold the blocker, do his job.
- Unblock operations that it blocked, with the same reason pointer
passed to bdrv_op_unblock().
- Release the blocker with error_free().
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Benoit Canet <benoit@irqsave.net>
Reviewed-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'user-exec.c')
0 files changed, 0 insertions, 0 deletions