[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remov
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action |
Date: |
Mon, 17 Jun 2019 18:03:19 +0200 |
User-agent: |
Mutt/1.11.3 (2019-02-01) |
Am 17.06.2019 um 13:37 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 08.06.2019 1:26, John Snow wrote:
> >
> >
> > On 6/3/19 8:00 AM, Vladimir Sementsov-Ogievskiy wrote:
> >> Hi all!
> >>
> >> Here is block-dirty-bitmap-remove transaction action.
> >>
> >> It is used to do transactional movement of the bitmap (which is
> >> possible in conjunction with merge command). Transactional bitmap
> >> movement is needed in scenarios with external snapshot, when we don't
> >> want to leave copy of the bitmap in the base image.
> >>
> >
> > Oh, interesting. I see why you want this now. OK, let's do it.
> >
>
>
> Hi John!
>
> Hmm, could you stage it, or should I fix something? Seems I've answered all
> questions.
> We need this for our nearest release and wanting to avoid x-vz- prefixes in
> the API,
> I'd be very grateful if we merge it soon.
I hope you won't have to do this, but in any case x-vz- isn't the right
prefix. Please read section '6. Downstream extension of QMP' in
docs/interop/qmp-spec.txt before adding your own extensions.
According to the spec, your prefix would be something like
__com.virtuozzo-...
Kevin
- Re: [Qemu-block] [Qemu-devel] [PATCH 1/4] blockdev: reduce aio_context locked sections in bitmap add/remove, (continued)
Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action, John Snow, 2019/06/07
Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action, John Snow, 2019/06/27