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 V14 06/15] monitor: track IOThread users with QOM paths
Date: Tue, 01 Sep 2026 07:47:01 +0200 [thread overview]
Message-ID: <8733vtbk16.fsf@pond.sub.org> (raw)
In-Reply-To: <20260831160038.221776-7-zhangckid@gmail.com> (Zhang Chen's message of "Tue, 1 Sep 2026 00:00:27 +0800")
Zhang Chen <zhangckid@gmail.com> writes:
> Monitors that require an IOThread share the internal mon_iothread.
> Account for each monitor explicitly in IOThread holder tracking, using
> the monitor's canonical QOM path to distinguish holders.
>
> Acquire the shared monitor IOThread AioContext once, using the monitor
> QOM path as the holder, and reuse the stored context for later
> operations.
>
> Release the holder from the Monitor ObjectClass::unparent callback,
> while the canonical QOM path is still available. This covers every
> object_unparent() path and avoids duplicating the cleanup in
> monitor_cleanup() and monitor_qmp_prepare_delete().
>
> The internal mon_iothread remains hidden from query-iothreads, as before.
> Management applications therefore cannot use it to determine which
> monitors are using the IOThread. Nevertheless, track the monitor
> holders so that they follow the same explicit holder and
> IOThread reference lifecycle as other AioContext users.
>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>
I have a question for our QOM experts (Paolo and Daniel).
This patch takes a reference in its UserCreatableClass method
complete(), and relinquishes it in its ObjectClass unparent() method.
Is that correct and clean? Or should complete() pair with
prepare_delete()?
> ---
> monitor/monitor-internal.h | 3 +++
> monitor/monitor.c | 33 ++++++++++++++++++++++++++++-----
> monitor/qmp.c | 5 +++--
> 3 files changed, 34 insertions(+), 7 deletions(-)
>
> diff --git a/monitor/monitor-internal.h b/monitor/monitor-internal.h
> index e0a124a317..74ea15c85f 100644
> --- a/monitor/monitor-internal.h
> +++ b/monitor/monitor-internal.h
> @@ -154,6 +154,9 @@ struct Monitor {
> guint out_watch;
> int mux_out;
> int reset_seen;
> +
> + /* iothread context */
> + AioContext *ctx;
> };
>
> struct MonitorHMPClass {
> diff --git a/monitor/monitor.c b/monitor/monitor.c
> index 6af09f2f6e..9e3b639eff 100644
> --- a/monitor/monitor.c
> +++ b/monitor/monitor.c
> @@ -81,6 +81,22 @@ int monitor_device_index;
> OBJECT_DEFINE_TYPE_EXTENDED(Monitor, monitor, MONITOR, OBJECT, true,
> { TYPE_USER_CREATABLE }, {});
>
> +static void monitor_unparent(Object *obj)
> +{
> + Monitor *mon = MONITOR(obj);
> +
> + if (mon->ctx && monitor_requires_iothread(mon)) {
> + g_autofree char *path = object_get_canonical_path(obj);
> + const IOThreadHolder io_holder = {
> + .type = IO_THREAD_HOLDER_KIND_QOM_OBJECT,
> + .u.qom_object.qom_path = path,
> + };
> +
> + iothread_unref_and_put_aio_context(mon_iothread, &io_holder);
> + mon->ctx = NULL;
> + }
> +}
> +
> static void monitor_finalize(Object *obj)
> {
> Monitor *mon = MONITOR(obj);
> @@ -116,6 +132,8 @@ static void monitor_class_init(ObjectClass *cls, const void *data)
> {
> UserCreatableClass *ucc = USER_CREATABLE_CLASS(cls);
>
> + cls->unparent = monitor_unparent;
> +
> object_class_property_add_str(cls, "chardev",
> monitor_get_chardev_id,
> monitor_set_chardev_id);
> @@ -575,7 +593,7 @@ void monitor_suspend(Monitor *mon)
> * Kick I/O thread to make sure this takes effect. It'll be
> * evaluated again in prepare() of the watch object.
> */
> - aio_notify(iothread_get_aio_context(mon_iothread));
> + aio_notify(mon->ctx);
> }
>
> trace_monitor_suspend(mon, 1);
> @@ -715,7 +733,6 @@ char *monitor_compat_id(void)
> static void monitor_complete(UserCreatable *uc, Error **errp)
> {
> Monitor *mon = MONITOR(uc);
> - AioContext *ctx;
>
> if (mon->chardev_id) {
> Chardev *chr = qemu_chr_find(mon->chardev_id);
> @@ -734,11 +751,17 @@ static void monitor_complete(UserCreatable *uc, Error **errp)
> mon_iothread = iothread_create("mon_iothread", &error_abort);
> }
>
> - ctx = iothread_get_aio_context(mon_iothread);
> + g_autofree char *path = object_get_canonical_path(OBJECT(mon));
> + const IOThreadHolder io_holder = {
> + .type = IO_THREAD_HOLDER_KIND_QOM_OBJECT,
> + .u.qom_object.qom_path = path,
> + };
> +
> + mon->ctx = iothread_ref_and_get_aio_context(mon_iothread, &io_holder);
> } else {
> - ctx = qemu_get_aio_context();
> + mon->ctx = qemu_get_aio_context();
> }
> - mon->accept_input_bh = aio_bh_new(ctx, monitor_accept_input, mon);
> + mon->accept_input_bh = aio_bh_new(mon->ctx, monitor_accept_input, mon);
> }
>
> int monitor_new(MonitorOptions *opts, bool allow_hmp, Error **errp)
> diff --git a/monitor/qmp.c b/monitor/qmp.c
> index aec0315775..de56345456 100644
> --- a/monitor/qmp.c
> +++ b/monitor/qmp.c
> @@ -734,7 +734,8 @@ static void monitor_qmp_complete(UserCreatable *uc, Error **errp)
> * thread. Schedule a bottom half.
> */
> mon->setup_pending = true;
> - aio_bh_schedule_oneshot(iothread_get_aio_context(mon_iothread),
> +
> + aio_bh_schedule_oneshot(MONITOR(mon)->ctx,
> monitor_qmp_setup_handlers_bh, mon);
> /* The bottom half will add @mon to @mon_list */
> } else {
> @@ -789,7 +790,7 @@ static bool monitor_qmp_prepare_delete(UserCreatable *uc, Error **errp)
>
> /* Synchronize with in-flight iothread callbacks. */
> if (monitor_requires_iothread(mon)) {
> - aio_wait_bh_oneshot(iothread_get_aio_context(mon_iothread),
> + aio_wait_bh_oneshot(MONITOR(mon)->ctx,
> monitor_qmp_iothread_quiesce, NULL);
> }
next prev parent reply other threads:[~2026-09-01 5:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 16:00 [PATCH V14 00/15] iothread: Support tracking and querying IOThread holder Zhang Chen
2026-08-31 16:00 ` [PATCH V14 01/15] qapi/misc: Fix missed query-iothreads items Zhang Chen
2026-08-31 16:00 ` [PATCH V14 02/15] iothread: introduce holder tracking Zhang Chen
2026-08-31 16:00 ` [PATCH V14 03/15] iothread: add holder-aware AioContext accessors Zhang Chen
2026-09-01 5:18 ` Markus Armbruster
2026-08-31 16:00 ` [PATCH V14 04/15] iothread: introduce iothread_unsafe_get_aio_context() Zhang Chen
2026-09-01 5:30 ` Markus Armbruster
2026-09-01 14:39 ` Zhang Chen
2026-09-02 10:46 ` Markus Armbruster
2026-08-31 16:00 ` [PATCH V14 05/15] block/export: track IOThread references Zhang Chen
2026-09-02 19:20 ` Stefan Hajnoczi
2026-08-31 16:00 ` [PATCH V14 06/15] monitor: track IOThread users with QOM paths Zhang Chen
2026-09-01 5:47 ` Markus Armbruster [this message]
2026-09-01 14:47 ` Zhang Chen
2026-09-02 11:25 ` Markus Armbruster
2026-09-02 11:53 ` Daniel P. Berrangé
2026-09-02 14:37 ` Markus Armbruster
2026-09-02 16:17 ` Daniel P. Berrangé
2026-09-04 8:33 ` Markus Armbruster
2026-09-04 8:57 ` Daniel P. Berrangé
2026-09-04 9:37 ` Zhang Chen
2026-09-02 19:35 ` Stefan Hajnoczi
2026-09-03 6:05 ` Markus Armbruster
2026-09-03 13:42 ` Stefan Hajnoczi
2026-09-03 14:52 ` Zhang Chen
2026-08-31 16:00 ` [PATCH V14 07/15] virtio-vq-mapping: track iothread-vq-mapping references using device path Zhang Chen
2026-08-31 16:00 ` [PATCH V14 08/15] virtio: track IOThread references for thread pinning Zhang Chen
2026-08-31 16:00 ` [PATCH V14 09/15] net/colo: track IOThread references using path-based holder Zhang Chen
2026-08-31 16:00 ` [PATCH V14 10/15] virtio-balloon: Update tracking iothread users with holder Zhang Chen
2026-08-31 16:00 ` [PATCH V14 11/15] vfio-user/proxy: Update tracking iothread users with holder name Zhang Chen
2026-08-31 16:00 ` [PATCH V14 12/15] xen-block: " Zhang Chen
2026-08-31 16:00 ` [PATCH V14 13/15] monitor/hmp: display IOThread holders Zhang Chen
2026-08-31 16:00 ` [PATCH V14 14/15] iothread: remove legacy iothread_get_aio_context() Zhang Chen
2026-09-01 5:35 ` Markus Armbruster
2026-09-01 14:39 ` Zhang Chen
2026-08-31 16:00 ` [PATCH V14 15/15] 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=8733vtbk16.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.