From: Markus Armbruster <armbru@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Eric Blake" <eblake@redhat.com>,
"'Michael S . Tsirkin'" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"'Daniel P . Berrangé'" <berrange@redhat.com>,
"Jason Wang" <jasowangio@gmail.com>
Subject: Re: [PATCH V15 13/14] iothread: make legacy AioContext getter explicitly unsafe
Date: Mon, 07 Sep 2026 14:55:51 +0200 [thread overview]
Message-ID: <87zextw78o.fsf@pond.sub.org> (raw)
In-Reply-To: <20260907063725.626685-14-zhangckid@gmail.com> (Zhang Chen's message of "Mon, 7 Sep 2026 14:37:24 +0800")
Zhang Chen <zhangckid@gmail.com> writes:
> Now that holder-aware callers have been converted, rename
> iothread_get_aio_context() to iothread_unsafe_get_aio_context() and
> update qmp_x_blockdev_set_iothread(). This avoids adding a duplicate
> accessor only to remove the old one later.
The last sentence appears to justify the change since v14. If that's
the intent, drop it, please. If not, what is the intent?
> The block graph retains only the AioContext, while detachment happens
> outside qmp_x_blockdev_set_iothread(), so this call site cannot provide
> a matching holder lifecycle. The new name makes its existing lifetime
> assumption explicit.
Suggest to start like "The only remaining user is
qmp_x_blockdev_set_iothread()" and then explain why this caller cannot
use iothread_ref_and_get_aio_context().
> New code should use iothread_ref_and_get_aio_context().
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>
> ---
> blockdev.c | 7 ++++++-
> include/system/iothread.h | 11 ++++++++++-
> iothread.c | 2 +-
> 3 files changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/blockdev.c b/blockdev.c
> index 6e86c6262f..97d161079a 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -3683,7 +3683,12 @@ void qmp_x_blockdev_set_iothread(const char *node_name, StrOrNull *iothread,
> goto out;
> }
>
> - new_context = iothread_get_aio_context(obj);
> + /*
> + * The block graph retains only the AioContext, not the IOThread.
> + * Context detachment happens outside this command, so there is no
> + * point here where a matching IOThread holder can be released.
> + */
This is fine for readers who already know what this is about: why we
can't use iothread_ref_and_get_aio_context() /
iothread_unsafe_get_aio_context() here. Others will lack context.
Suggest to start like
/*
* We cannot use iothread_ref_and_get_aio_context() /
* iothread_unref_and_put_aio_context() here.
then explain why.
> + new_context = iothread_unsafe_get_aio_context(obj);
> } else {
> new_context = qemu_get_aio_context();
> }
[...]
next prev parent reply other threads:[~2026-09-07 12:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:37 [PATCH V15 00/14] iothread: Support tracking and querying IOThread holder Zhang Chen
2026-09-07 6:37 ` [PATCH V15 01/14] qapi/misc: Fix missed query-iothreads items Zhang Chen
2026-09-07 7:24 ` Michael Tokarev
2026-09-10 5:28 ` Zhang Chen
2026-09-10 6:01 ` Markus Armbruster
2026-09-07 6:37 ` [PATCH V15 02/14] iothread: introduce holder tracking Zhang Chen
2026-09-07 6:37 ` [PATCH V15 03/14] iothread: add holder-aware AioContext accessors Zhang Chen
2026-09-07 6:37 ` [PATCH V15 04/14] block/export: track IOThread references Zhang Chen
2026-09-07 6:37 ` [PATCH V15 05/14] monitor: track IOThread users with QOM paths Zhang Chen
2026-09-07 12:44 ` Markus Armbruster
2026-09-09 7:57 ` Zhang Chen
2026-09-09 10:40 ` Markus Armbruster
2026-09-10 2:24 ` Zhang Chen
2026-09-10 4:42 ` Markus Armbruster
2026-09-07 6:37 ` [PATCH V15 06/14] virtio-vq-mapping: track iothread-vq-mapping references using device path Zhang Chen
2026-09-07 6:37 ` [PATCH V15 07/14] virtio: track IOThread references for thread pinning Zhang Chen
2026-09-07 6:37 ` [PATCH V15 08/14] net/colo: track IOThread references using path-based holder Zhang Chen
2026-09-07 6:37 ` [PATCH V15 09/14] virtio-balloon: Update tracking iothread users with holder Zhang Chen
2026-09-07 6:37 ` [PATCH V15 10/14] vfio-user/proxy: Update tracking iothread users with holder name Zhang Chen
2026-09-07 6:37 ` [PATCH V15 11/14] xen-block: " Zhang Chen
2026-09-07 6:37 ` [PATCH V15 12/14] monitor/hmp: display IOThread holders Zhang Chen
2026-09-07 6:37 ` [PATCH V15 13/14] iothread: make legacy AioContext getter explicitly unsafe Zhang Chen
2026-09-07 12:55 ` Markus Armbruster [this message]
2026-09-09 6:24 ` Zhang Chen
2026-09-09 10:41 ` Markus Armbruster
2026-09-07 6:37 ` [PATCH V15 14/14] tests/unit/iothread: update AioContext ref/put helpers Zhang Chen
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=87zextw78o.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowangio@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhangckid@gmail.com \
/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.