Re: [PATCH RFC 00/17] monitor: turn QMP and HMP into QOM objects

["Daniel P. Berrangé" <berrange@redhat.com>]

On Mon, Apr 27, 2026 at 08:35:41AM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
> > Conceptually -object and object_add/object_del should be sufficient
> > for essentially all QEMU configuration....if only we ported all our
> > internal custom backends/devices/etc to QOM. That is of course a big
> > job which is why it hasn't happened.
> 
> In addition, we'd need a more unified object life cycle.  See "Problem
> 5: QOM lacks a clear life cycle" in
> 
>     Subject: Dynamic & heterogeneous machines, initial configuration: problems
>     Date: Wed, 31 Jan 2024 21:14:21 +0100
>     Message-ID: <87o7d1i7ky.fsf@pond.sub.org>
>     https://lore.kernel.org/qemu-devel/87o7d1i7ky.fsf@pond.sub.org/
> 
> > This series started with the premise that the monitor is one of the
> > easier areas to convert since we have no more than three classes,
> > a common base, and QMP and HMP subclasses. So why not give it a go
> > and thus unlock the ability to dynamically create/delete monitors
> > in QMP/HMP.
> 
> Makes sense.
> 
> > This series does the conversion in as many small steps as I could
> > achieve. At the end it is possible to create HMP and QMP monitors
> > with -object and object_add.
> 
> I'll try to squeeze in review.

Don't review this v1 yet. I've got a v2 I'm finishing off to send
real soon.