Searched hist:bddcec3745b0220d4a7eda700950812a94398668 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/include/block/ |
| H A D | block_int.h | diff bddcec3745b0220d4a7eda700950812a94398668 Thu Apr 09 11:47:50 CDT 2015 Kevin Wolf <kwolf@redhat.com> block: Add BlockDriverState.inherits_from
Currently, the block layer assumes that any block node can have only one
parent, and if it has a parent, that it inherits some options/flags from
this parent.
This is not true any more: With references used in block device
creation, a single node can be used by multiple parents, or it can be
created separately and not inherit flags from any parent.
To handle reopens correctly, a node must know from which parent it
inherited options. This patch adds the information to BlockDriverState.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
|
| /openbmc/qemu/ |
| H A D | block.c | diff bddcec3745b0220d4a7eda700950812a94398668 Thu Apr 09 11:47:50 CDT 2015 Kevin Wolf <kwolf@redhat.com> block: Add BlockDriverState.inherits_from
Currently, the block layer assumes that any block node can have only one
parent, and if it has a parent, that it inherits some options/flags from
this parent.
This is not true any more: With references used in block device
creation, a single node can be used by multiple parents, or it can be
created separately and not inherit flags from any parent.
To handle reopens correctly, a node must know from which parent it
inherited options. This patch adds the information to BlockDriverState.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
|