Hi,
I'm late to the party but I wanted to say that I generally like the idea
of expressing the notion of op blockers in terms of the specific things
that they allow and require in each one of the affected nodes.
I don't know if all current operations can be expressed easily with
these semantics,
On Fri, Dec 18, 2015 at 03:19:25PM +0100, Kevin Wolf wrote:
> Am 16.12.2015 um 07:25 hat Jeff Cody geschrieben:
> > Background:
> >
> > Block jobs, and other QAPI operations, may modify and impact the
> > BlockDriverState graph in QEMU. In order to support multiple
> > operations safe
Am 16.12.2015 um 07:25 hat Jeff Cody geschrieben:
> Background:
>
> Block jobs, and other QAPI operations, may modify and impact the
> BlockDriverState graph in QEMU. In order to support multiple
> operations safely, we need a mechanism to block and gate operations,
>
> We currently
On Wed, Dec 16, 2015 at 01:25:29AM -0500, Jeff Cody wrote:
> Background:
>
> Block jobs, and other QAPI operations, may modify and impact the
> BlockDriverState graph in QEMU. In order to support multiple
> operations safely, we need a mechanism to block and gate operations,
>
> We c
Background:
Block jobs, and other QAPI operations, may modify and impact the
BlockDriverState graph in QEMU. In order to support multiple
operations safely, we need a mechanism to block and gate operations,
We currently have op blockers, that are attached to each BDS.
However, in pra
