From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, hreitz@redhat.com, pkrempa@redhat.com,
peterx@redhat.com, farosas@suse.de, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 11/15] block/export: Add option to allow export of inactive nodes
Date: Mon, 3 Feb 2025 14:17:20 -0500 [thread overview]
Message-ID: <20250203191720.GM268514@fedora> (raw)
In-Reply-To: <20250131095051.49708-2-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
On Fri, Jan 31, 2025 at 10:50:47AM +0100, Kevin Wolf wrote:
> Add an option in BlockExportOptions to allow creating an export on an
> inactive node without activating the node. This mode needs to be
> explicitly supported by the export type (so that it doesn't perform any
> operations that are forbidden for inactive nodes), so this patch alone
> doesn't allow this option to be successfully used yet.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> qapi/block-export.json | 10 +++++++++-
> include/block/block-global-state.h | 3 +++
> include/block/export.h | 3 +++
> block.c | 4 ++++
> block/export/export.c | 31 ++++++++++++++++++++----------
> 5 files changed, 40 insertions(+), 11 deletions(-)
>
> diff --git a/qapi/block-export.json b/qapi/block-export.json
> index ce33fe378d..117b05d13c 100644
> --- a/qapi/block-export.json
> +++ b/qapi/block-export.json
> @@ -372,6 +372,13 @@
> # cannot be moved to the iothread. The default is false.
> # (since: 5.2)
> #
> +# @allow-inactive: If true, the export allows the exported node to be inactive.
> +# If it is created for an inactive block node, the node remains inactive. If
> +# the export type doesn't support running on an inactive node, an error is
> +# returned. If false, inactive block nodes are automatically activated before
> +# creating the export and trying to inactivate them later fails.
> +# (since: 10.0; default: false)
Exposing activation in the API is ugly but I don't see a cleaner option
given that we cannot change block-export-add's existing behavior of
activating the node by default. :(
Ideally block-export-add would not modify active/inactive and leave it
up to user to provide a node in the desired state.
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-03 19:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 17:12 [PATCH v2 00/15] block: Managing inactive nodes (QSD migration) Kevin Wolf
2025-01-30 17:12 ` [PATCH v2 01/15] block: Add 'active' field to BlockDeviceInfo Kevin Wolf
2025-01-30 19:30 ` Eric Blake
2025-02-03 18:47 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 02/15] block: Inactivate external snapshot overlays when necessary Kevin Wolf
2025-01-30 19:46 ` Eric Blake
2025-02-03 18:48 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 03/15] migration/block-active: Remove global active flag Kevin Wolf
2025-01-30 19:50 ` Eric Blake
2025-02-04 15:50 ` Kevin Wolf
2025-02-03 18:49 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 04/15] block: Don't attach inactive child to active node Kevin Wolf
2025-01-30 20:08 ` Eric Blake
2025-02-03 18:50 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 05/15] block: Allow inactivating already inactive nodes Kevin Wolf
2025-01-30 20:09 ` Eric Blake
2025-02-03 18:51 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 06/15] block: Fix crash on block_resize on inactive node Kevin Wolf
2025-01-30 20:11 ` Eric Blake
2025-02-03 18:52 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 07/15] block: Add option to create inactive nodes Kevin Wolf
2025-01-30 20:17 ` Eric Blake
2025-02-03 18:53 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 08/15] block: Add blockdev-set-active QMP command Kevin Wolf
2025-01-30 20:22 ` Eric Blake
2025-02-03 18:54 ` Stefan Hajnoczi
2025-01-30 17:12 ` [PATCH v2 09/15] block: Support inactive nodes in blk_insert_bs() Kevin Wolf
2025-01-30 20:26 ` Eric Blake
2025-02-03 18:55 ` Stefan Hajnoczi
2025-01-31 9:50 ` [PATCH v2 10/15] block/export: Don't ignore image activation error in blk_exp_add() Kevin Wolf
2025-02-03 16:30 ` Eric Blake
2025-02-03 18:58 ` Stefan Hajnoczi
2025-02-04 15:54 ` Kevin Wolf
2025-01-31 9:50 ` [PATCH v2 11/15] block/export: Add option to allow export of inactive nodes Kevin Wolf
2025-01-31 13:41 ` Fabiano Rosas
2025-02-04 15:44 ` Kevin Wolf
2025-02-03 19:12 ` Eric Blake
2025-02-03 19:17 ` Stefan Hajnoczi [this message]
2025-01-31 9:50 ` [PATCH v2 12/15] nbd/server: Support " Kevin Wolf
2025-02-03 19:17 ` Eric Blake
2025-02-03 19:19 ` Stefan Hajnoczi
2025-02-04 17:10 ` Kevin Wolf
2025-01-31 9:50 ` [PATCH v2 13/15] iotests: Add filter_qtest() Kevin Wolf
2025-02-03 19:19 ` Eric Blake
2025-01-31 9:50 ` [PATCH v2 14/15] iotests: Add qsd-migrate case Kevin Wolf
2025-02-03 19:35 ` Eric Blake
2025-02-03 21:09 ` Kevin Wolf
2025-01-31 9:50 ` [PATCH v2 15/15] iotests: Add (NBD-based) tests for inactive nodes Kevin Wolf
2025-02-03 19:49 ` Eric Blake
2025-02-04 16:30 ` Kevin Wolf
2025-01-31 13:53 ` [PATCH v2 00/15] block: Managing inactive nodes (QSD migration) Fabiano Rosas
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=20250203191720.GM268514@fedora \
--to=stefanha@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peterx@redhat.com \
--cc=pkrempa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.