All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [RESEND PATCH V3 3/3] qapi: Add attached flag for iothread
Date: Wed, 04 Feb 2026 13:58:16 +0100	[thread overview]
Message-ID: <877bssy8bb.fsf@pond.sub.org> (raw)
In-Reply-To: <20260126094422.23116-3-zhangckid@gmail.com> (Zhang Chen's message of "Mon, 26 Jan 2026 17:44:22 +0800")

Zhang Chen <zhangckid@gmail.com> writes:

> The attached flag depends on struct IOThreadInfo's
> 'attached': 'bool'. It can show whether the iothread
> is attached to an actual device. Show in the qmp/hmp
> CMD with "attached": true/false.
>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>

[...]

> diff --git a/qapi/misc.json b/qapi/misc.json
> index 1f5062df2a..cb865d6e48 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -76,6 +76,15 @@
>  #
>  # @thread-id: ID of the underlying host thread
>  #
> +# @attached: The attached parameter is a flag indicating whether
> +#     the IOThread is currently associated with an active device

"the iothread" for consistency with other doc text.

> +#     (e.g., virtio-blk).  In hotplug scenarios, users can

I'd drop the comma.

> +#     pre-allocate multiple iothread objects to serve as a persistent
> +#     thread pool.  When a device is hot-unplugged, the corresponding
> +#     IOThread is released but remains available, allowing subsequent
> +#     hot-plugged devices to attach to and reuse the existing thread.
> +#     (since 12.0)

(since 11.0)

> +#
>  # @poll-max-ns: maximum polling time in ns, 0 means polling is
>  #     disabled (since 2.9)
>  #
> @@ -93,6 +102,7 @@
>  { 'struct': 'IOThreadInfo',
>    'data': {'id': 'str',
>             'thread-id': 'int',
> +           'attached': 'bool',
>             'poll-max-ns': 'int',
>             'poll-grow': 'int',
>             'poll-shrink': 'int',
> @@ -118,6 +128,7 @@
>  #              {
>  #                 "id":"iothread0",
>  #                 "thread-id":3134,
> +#                 "attached":false,
>  #                 "poll-max-ns":32768,
>  #                 "poll-grow":0,
>  #                 "poll-shrink":0,
> @@ -126,6 +137,7 @@
>  #              {
>  #                 "id":"iothread1",
>  #                 "thread-id":3135,
> +#                 "attached":true,
>  #                 "poll-max-ns":32768,
>  #                 "poll-grow":0,
>  #                 "poll-shrink":0,

With that
Acked-by: Markus Armbruster <armbru@redhat.com>



  reply	other threads:[~2026-02-04 12:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26  9:44 [RESEND PATCH V3 1/3] qapi/misc: Fix missed query-iothreads items Zhang Chen
2026-01-26  9:44 ` [RESEND PATCH V3 2/3] iothread: Introduce a new flag to show iothreads attached status Zhang Chen
2026-02-05 16:11   ` Stefan Hajnoczi
2026-02-06  3:20     ` Zhang Chen
2026-01-26  9:44 ` [RESEND PATCH V3 3/3] qapi: Add attached flag for iothread Zhang Chen
2026-02-04 12:58   ` Markus Armbruster [this message]
2026-02-05  2:49     ` Zhang Chen
2026-02-05  6:55       ` Markus Armbruster
2026-02-05 16:25   ` Stefan Hajnoczi
2026-02-06  3:47     ` Zhang Chen
2026-02-04 12:53 ` [RESEND PATCH V3 1/3] qapi/misc: Fix missed query-iothreads items Markus Armbruster

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=877bssy8bb.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dave@treblig.org \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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.