From: Markus Armbruster <armbru@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Dr . David Alan Gilbert" <dave@treblig.org>,
Eric Blake <eblake@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH V6 13/14] qapi: examine IOThread attachment status via query-iothreads
Date: Thu, 23 Apr 2026 15:09:53 +0200 [thread overview]
Message-ID: <87340lomam.fsf@pond.sub.org> (raw)
In-Reply-To: <20260410150457.85190-14-zhangckid@gmail.com> (Zhang Chen's message of "Fri, 10 Apr 2026 23:04:56 +0800")
Zhang Chen <zhangckid@gmail.com> writes:
> Extend the 'IOThreadInfo' structure to include attachment metrics.
> This allows users to monitor the associated devices by identify them
> by their QOM paths.
>
> New fields added to IOThreadInfo:
> - @holders: IoThreadHolder(QOM path or block node name) of the devices
> currently associated with this iothread.
See "I'm confused" below.
>
> These fields are also exposed via the Human Monitor Interface (HMP)
> command 'info iothreads' to assist with manual debugging and
> performance tuning.
>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>
[...]
> diff --git a/qapi/misc.json b/qapi/misc.json
> index d65d8012b2..e173d54a5e 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -94,7 +94,8 @@
> # @IoThreadHolderKind:
> #
> # @block-node: Block node name.
> -# @qom-object: Standard QOM path.
> +#
> +# @qom-object: QOM path.
> #
> # Since: 11.0
> ##
Squash this into PATCH 02, please.
> @@ -104,7 +105,7 @@
> ##
> # @IoThreadHolder:
> #
> -# @type: Current IoThread holder type support QOM path and Block node.
> +# @type: Current IoThread holder type support QOM path and block node.
This, too.
> #
> # Since: 11.0
> ##
> @@ -124,6 +125,13 @@
> #
> # @thread-id: ID of the underlying host thread
> #
> +# @holders: IoThreadHolder(QOM path or block node name) of the devices
Space before (
> +# currently associated with this iothread. Users can pre-allocate
I'm confused. What is holding what?
A QOM object / block node / monitor holding an I/O thread?
> +# multiple iothread objects to serve as a persistent thread pool.
> +# When a device is hot-unplugged, it is detached from its
> +# iothread, but the iothread remains available, allowing future
> +# hot-plugged devices to attach to it.
> +#
> # @poll-max-ns: maximum polling time in ns, 0 means polling is
> # disabled (since 2.9)
> #
> @@ -141,6 +149,7 @@
> { 'struct': 'IOThreadInfo',
> 'data': {'id': 'str',
> 'thread-id': 'int',
> + 'holders': ['IoThreadHolder'],
> 'poll-max-ns': 'int',
> 'poll-grow': 'int',
> 'poll-shrink': 'int',
> @@ -166,6 +175,8 @@
> # {
> # "id":"iothread0",
> # "thread-id":3134,
> +# "holders":["/machine/peripheral/blk1/virtio-backend",
> +# "/machine/peripheral/blk0/virtio-backend"],
> # "poll-max-ns":32768,
> # "poll-grow":0,
> # "poll-shrink":0,
> @@ -174,6 +185,7 @@
> # {
> # "id":"iothread1",
> # "thread-id":3135,
> +# "holders":["/machine/peripheral/blk2/virtio-backend"],
> # "poll-max-ns":32768,
> # "poll-grow":0,
> # "poll-shrink":0,
next prev parent reply other threads:[~2026-04-23 13:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 15:04 [PATCH V6 00/14] iothread: Support tracking and querying IOThread holders Zhang Chen
2026-04-10 15:04 ` [PATCH V6 01/14] qapi/misc: Fix missed query-iothreads items Zhang Chen
2026-04-10 15:04 ` [PATCH V6 02/14] iothread: introduce iothread_ref/unref to track attached devices Zhang Chen
2026-04-21 14:15 ` Markus Armbruster
2026-04-27 14:55 ` Zhang Chen
2026-04-10 15:04 ` [PATCH V6 03/14] iothread: tracking iothread users with holder name Zhang Chen
2026-04-10 15:04 ` [PATCH V6 04/14] blockdev: Update " Zhang Chen
2026-04-10 15:04 ` [PATCH V6 05/14] block/export: track IOThread reference in BlockExport Zhang Chen
2026-04-10 15:04 ` [PATCH V6 06/14] monitor: Update tracking iothread users with holder name Zhang Chen
2026-04-23 12:44 ` Markus Armbruster
2026-04-27 14:55 ` Zhang Chen
2026-04-28 7:26 ` Markus Armbruster
2026-04-29 5:34 ` Zhang Chen
2026-04-10 15:04 ` [PATCH V6 07/14] virtio-vq-mapping: track iothread-vq-mapping references using device path Zhang Chen
2026-04-10 15:04 ` [PATCH V6 08/14] virtio: use iothread_get/put_aio_context for thread pinning Zhang Chen
2026-04-10 15:04 ` [PATCH V6 09/14] net/colo: track IOThread references using path-based holder Zhang Chen
2026-04-10 15:04 ` [PATCH V6 10/14] virtio-balloon: Update tracking iothread users with holder name Zhang Chen
2026-04-10 15:04 ` [PATCH V6 11/14] vfio-user/proxy: " Zhang Chen
2026-04-10 15:04 ` [PATCH V6 12/14] xen-block: " Zhang Chen
2026-04-10 15:04 ` [PATCH V6 13/14] qapi: examine IOThread attachment status via query-iothreads Zhang Chen
2026-04-23 13:09 ` Markus Armbruster [this message]
2026-04-27 15:10 ` Zhang Chen
2026-04-10 15:04 ` [PATCH V6 14/14] iothread: simplify API by merging iothread_get_aio_context variants 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=87340lomam.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=eblake@redhat.com \
--cc=mst@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.