Re: [PATCH 1/4] qdev: Pave way for exporting Property to be used in non-qdev

[Peter Xu <peterx@redhat.com>]

On Fri, Jun 05, 2026 at 11:39:26AM -0300, Fabiano Rosas wrote:
> Peter Xu <peterx@redhat.com> writes:
> 
> > Property itself is a well defined interface to either support smooth
> > conversions to Object's properties, or supports global properties.  However
> > currently it's tied to DeviceClass, aka, qdev. So non-qdev cannot use
> > Property list.
> >
> > My current observation shows Property is almost ready to be used as a
> > separated exported interface, except two small things that may need touch
> > up internally:
> >
> >         qdev_prop_allow_set
> 
> Just a thought, we could use something like this to block update of
> migration parameters during migration runtime.

Currently it may not achieve it (with qdev property or object property that
I'm trying), it's because qmp set parameters currently bypasses qom
properties.

We need to switch QMP set parameters to use qom set to achieve it, but yes,
that sounds like something good to consider in the future to merge the two
paths somehow.

If we use helpers like object_property_add_uint64_ptr() we save lines but
lose control over setter() blocking updates during live migration.  If we
use raw object_property_add() we get control but adds boilerplate lines.

Anyway, sounds like something for the future..

-- 
Peter Xu