From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: mreitz@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: Re: Plans to bring QMP 'x-blockdev-reopen' out of experimental?
Date: Tue, 20 Oct 2020 10:23:33 +0200 [thread overview]
Message-ID: <20201020082333.GB4452@merkur.fritz.box> (raw)
In-Reply-To: <w51k0vmf9k3.fsf@maestria.local.igalia.com>
Am 19.10.2020 um 18:46 hat Alberto Garcia geschrieben:
> On Mon 19 Oct 2020 05:56:56 PM CEST, Alberto Garcia wrote:
> > And this one in particular:
> >
> > https://lists.gnu.org/archive/html/qemu-block/2020-02/msg00601.html
>
> I forgot to add, we still don't support changing bs->file with this
> command, so I guess that would be one blocker?
>
> There's no other way of inserting filter nodes, or is there?
Not that I'm aware of.
So yes, changing bs->file is the one thing I had in mind for
implementing before we mark it stable.
I'm not entirely sure if we should make some restrictions or allow
arbitrary changes. If it's only about filters, we could check that the
node returned by bdrv_skip_filters() stays the same. This would be
almost certainly safe (if the chain is not frozen, of course).
If people want to dynamically insert non-filters (maybe quorum?), it
might be more restrictive than necessary, though.
Other cases like inserting a qcow2 file in the chain where the old child
becomes the backing file of the newly inserted node should in theory
already be covered by blockdev-snapshot.
Kevin
next prev parent reply other threads:[~2020-10-20 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201006091001.GA64583@paraplu>
2020-10-19 15:56 ` Plans to bring QMP 'x-blockdev-reopen' out of experimental? Alberto Garcia
2020-10-19 16:46 ` Alberto Garcia
2020-10-20 8:23 ` Kevin Wolf [this message]
2020-10-20 11:53 ` Alberto Garcia
2020-10-21 10:48 ` Kevin Wolf
2020-12-02 16:12 ` Alberto Garcia
2020-12-02 16:28 ` Kevin Wolf
2020-12-02 16:40 ` Alberto Garcia
2020-12-02 17:51 ` Kevin Wolf
2020-12-04 14:03 ` Alberto Garcia
2020-10-20 8:20 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201020082333.GB4452@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=kchamart@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).