[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH 16/19] block: Allow graph changes in subtree dra
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-block] [PATCH 16/19] block: Allow graph changes in subtree drained section |
Date: |
Wed, 20 Dec 2017 12:18:22 +0100 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
Am 20.12.2017 um 11:51 hat Paolo Bonzini geschrieben:
> On 20/12/2017 11:34, Kevin Wolf wrote:
> > .inherit_options = bdrv_inherited_options,
> > .drained_begin = bdrv_child_cb_drained_begin,
> > .drained_end = bdrv_child_cb_drained_end,
> > + .attach = bdrv_child_cb_attach,
> > + .detach = bdrv_child_cb_detach,
> > .inactivate = bdrv_child_cb_inactivate,
> > };
> >
> > @@ -911,6 +933,8 @@ const BdrvChildRole child_format = {
> > .inherit_options = bdrv_inherited_fmt_options,
> > .drained_begin = bdrv_child_cb_drained_begin,
> > .drained_end = bdrv_child_cb_drained_end,
> > + .attach = bdrv_child_cb_attach,
> > + .detach = bdrv_child_cb_detach,
> > .inactivate = bdrv_child_cb_inactivate,
>
> Is there any case of a BdrvChildRole that doesn't want these callbacks?
> Maybe the functions should be called after ->attach and before ->detach
> (e.g. bdrv_{,un}apply_subtree_drain), rather than modifying the
> BdrvChildRole implementations.
At first I intended to implement it directly in
bdrv_replace_child_noperm(), but the thing is that you need the
bs->recursive_quiesce_counter of the parent BDS - but not all parents of
a BdrvChild are even a BDS. It could also be a BB root child or a block
job child. This is why we only have a void *opaque rather than a BDS
pointer for the parent.
The other option would be an additional BdrvChildRole callback like
.get_recursive_quiesce_counter, but compared to that, I like some code
in .attach/.detach better.
> Then they can be put in block/io.c, and bdrv_do_drained_* can remain
> static. (I would also consider extracting block/drain.c, but it is
> painful to do it now that you have this nice series---so let's do it after).
I can keep that in mind for part 3 (or 4, whatever it may become).
Kevin
- Re: [Qemu-block] [Qemu-devel] [PATCH 11/19] block: Don't notify parents in drain call chain, (continued)
- [Qemu-block] [PATCH 10/19] test-bdrv-drain: Test nested drain sections, Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 12/19] block: Add bdrv_subtree_drained_begin/end(), Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 14/19] test-bdrv-drain: Test behaviour in coroutine context, Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 15/19] test-bdrv-drain: Recursive draining with multiple parents, Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 13/19] test-bdrv-drain: Tests for bdrv_subtree_drain, Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 17/19] test-bdrv-drain: Test graph changes in drained section, Kevin Wolf, 2017/12/20
- [Qemu-block] [PATCH 16/19] block: Allow graph changes in subtree drained section, Kevin Wolf, 2017/12/20
[Qemu-block] [PATCH 18/19] commit: Simplify reopen of base, Kevin Wolf, 2017/12/20
[Qemu-block] [PATCH 19/19] block: Keep nodes drained between reopen_queue/multiple, Kevin Wolf, 2017/12/20
Re: [Qemu-block] [PATCH 00/19] Drain fixes and cleanups, part 2, Paolo Bonzini, 2017/12/20