From: "Daniel P. Berrangé" <berrange@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>,
Markus Armbruster <armbru@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Jason Wang <jasowang@redhat.com>,
Fam Zheng <fam@euphon.net>
Subject: Re: [PATCH V9 06/17] monitor: refactor monitor_data_init() to pass ID
Date: Thu, 16 Jul 2026 13:48:59 +0100 [thread overview]
Message-ID: <aljTO75kKel2fVLx@redhat.com> (raw)
In-Reply-To: <CAK3tnvLTwLdWm2ZHcLhHRsncHZVvEgW_B14Ua4ZS9EX6BE1Erw@mail.gmail.com>
On Mon, Jun 29, 2026 at 04:31:56PM +0800, Zhang Chen wrote:
> On Fri, Jun 26, 2026 at 9:32 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Wed, Jun 24, 2026 at 03:08:40PM +0800, Zhang Chen wrote:
> > > Anonymous monitors (e.g., '-monitor stdio' or GDB stub) leave their 'id'
> > > field as NULL. To allow downstream subsystems (like iothread tracking) to
> > > identify these instances later, the initialization paths must propagate
> > > the context.
> > >
> > > Refactor monitor_data_init() to accept the 'id' parameters, and
> > > update all internal QMP/HMP paths to pass these identifiers.
> > >
> > > For anonymous monitors, 'mon->id' remains NULL at this stage to avoid
> > > namespace pollution, setting up infrastructure for subsequent patches.
> > >
> > > Signed-off-by: Zhang Chen <zhangckid@gmail.com>
> > > ---
> > > chardev/char.c | 2 +-
> > > gdbstub/system.c | 3 ++-
> > > include/monitor/monitor.h | 5 +++--
> > > monitor/hmp.c | 5 +++--
> > > monitor/monitor-internal.h | 4 +++-
> > > monitor/monitor.c | 9 ++++++---
> > > monitor/qmp-cmds.c | 2 +-
> > > monitor/qmp.c | 5 +++--
> > > stubs/monitor-internal.c | 3 ++-
> > > 9 files changed, 24 insertions(+), 14 deletions(-)
> >
> > This patch will significantly conflict with my series that
> > creates QOM objects for the monitors. They will all be
> > guaranteed to have an "id" at that point though, which
> > addresses the problem you're trying to solve IIUC.
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2026-06/msg06427.html
> >
>
> Thank you for your updates.
> As Markus's help, we already know your series for create
> QOM for the monitors. So this series V7 based on the assumption of
> your patch merged. But for the comments:
> "Feels like this patch should not be merged as is."
> https://lists.gnu.org/archive/html/qemu-devel/2026-05/msg04214.html
>
> I have to fix it by myself.
> I'm very happy this series based on your series, I can conveniently make
> the monitor as a regular QOM object like others in this series.
> If you think that OK, I will rebase my series on your QOM for monitor patches
> in next version.
FYI, my monitor hotplug series is merged, so you can simply
rebase your work onto current git HEAD.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-07-16 12:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 7:08 [PATCH V9 00/17] iothread: Support tracking and querying IOThread holders Zhang Chen
2026-06-24 7:08 ` [PATCH V9 01/17] qapi/misc: Fix missed query-iothreads items Zhang Chen
2026-06-24 7:08 ` [PATCH V9 02/17] iothread: introduce iothread_ref/unref to track attached devices Zhang Chen
2026-06-24 15:51 ` Stefan Hajnoczi
2026-06-24 22:47 ` Zhang Chen
2026-06-26 8:46 ` Markus Armbruster
2026-06-29 6:58 ` Zhang Chen
2026-06-29 10:42 ` Markus Armbruster
2026-07-06 9:06 ` Zhang Chen
2026-07-06 10:44 ` Markus Armbruster
2026-06-24 7:08 ` [PATCH V9 03/17] iothread: tracking iothread users with holder name Zhang Chen
2026-06-24 17:10 ` Stefan Hajnoczi
2026-06-24 22:48 ` Zhang Chen
2026-06-24 7:08 ` [PATCH V9 04/17] iothread: introduce iothread_unsafe_get_aio_context() Zhang Chen
2026-06-24 17:19 ` Stefan Hajnoczi
2026-06-24 22:47 ` Zhang Chen
2026-06-24 7:08 ` [PATCH V9 05/17] block/export: track IOThread reference in BlockExport Zhang Chen
2026-06-24 17:51 ` Stefan Hajnoczi
2026-06-24 23:06 ` Zhang Chen
2026-06-25 13:31 ` Stefan Hajnoczi
2026-06-25 15:16 ` Stefan Hajnoczi
2026-06-29 6:01 ` Zhang Chen
2026-07-01 16:10 ` Stefan Hajnoczi
2026-06-24 7:08 ` [PATCH V9 06/17] monitor: refactor monitor_data_init() to pass ID Zhang Chen
2026-06-26 13:04 ` Markus Armbruster
2026-06-26 13:31 ` Daniel P. Berrangé
2026-06-29 8:31 ` Zhang Chen
2026-07-16 12:48 ` Daniel P. Berrangé [this message]
2026-07-16 14:48 ` Zhang Chen
2026-06-24 7:08 ` [PATCH V9 07/17] monitor: support iothread ref/unref for anonymous monitors Zhang Chen
2026-06-24 7:08 ` [PATCH V9 08/17] monitor: switch to iothread_unsafe_get_aio_context() Zhang Chen
2026-07-01 16:16 ` Stefan Hajnoczi
2026-07-06 8:59 ` Zhang Chen
2026-07-16 9:22 ` Stefan Hajnoczi
2026-07-16 14:53 ` Zhang Chen
2026-06-24 7:08 ` [PATCH V9 09/17] virtio-vq-mapping: track iothread-vq-mapping references using device path Zhang Chen
2026-06-24 7:08 ` [PATCH V9 10/17] virtio: use iothread_get/put_aio_context for thread pinning Zhang Chen
2026-06-24 7:08 ` [PATCH V9 11/17] net/colo: track IOThread references using path-based holder Zhang Chen
2026-06-24 7:08 ` [PATCH V9 12/17] virtio-balloon: Update tracking iothread users with holder Zhang Chen
2026-06-24 7:08 ` [PATCH V9 13/17] vfio-user/proxy: Update tracking iothread users with holder name Zhang Chen
2026-06-24 7:08 ` [PATCH V9 14/17] xen-block: " Zhang Chen
2026-06-24 7:08 ` [PATCH V9 15/17] qapi: examine IOThread attachment status via query-iothreads Zhang Chen
2026-06-24 7:08 ` [PATCH V9 16/17] iothread: simplify API by merging iothread_get_aio_context variants Zhang Chen
2026-06-24 7:08 ` [PATCH V9 17/17] tests/unit/iothread: Update the iothread_get_aio_context 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=aljTO75kKel2fVLx@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.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.