From: Zhao Liu <zhao1.liu@intel.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Markus Armbruster" <armbru@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Mark Cave-Ayland" <mark.caveayland@nutanix.com>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Zide Chen" <zide.chen@intel.com>,
"Dapeng Mi" <dapeng1.mi@linux.intel.com>,
qemu-devel@nongnu.org, devel@lists.libvirt.org,
"Zhao Liu" <zhao1.liu@intel.com>
Subject: Re: [PATCH v2 14/21] hw/core/qdev-properties: allow qdev properties accept flags
Date: Mon, 9 Mar 2026 21:34:42 +0800 [thread overview]
Message-ID: <aa7Mckq/8cgwZwkB@intel.com> (raw)
In-Reply-To: <aY309kPru8ELO5_N@redhat.com>
(Sorry for the long silence — just returned from vacation.)
> > Yeah, most property setting paths are covered by
> > object_set_properties_from_qdict() (I listes these cases in patch 12,
> > including the most common ones: -object/-device and their related HMP/QMP
> > commands).
> >
> > But there're some corner cases which don't go through
> > object_set_properties_from_qdict(), e.g., -global/-accel/"qom-set", etc,
> > those were considerred in patch 9/11/13 (and sorry I should list all
> > cases affected in cover letter :(). These cases are where I find
> > things to be both trivial and tricky, so I manually check them and mark
> > them using USER_SET.
> >
> > Therefore, I think the unified entry point for externally setting
> > properties resides at a lower level—specifically, is object_property_set(),
> > then we need to dientify when object_property_set() is called by
> > external user or not - that's how USER_SET works...(I feel like I'm back
> > where I started).
>
> There's a significant different there. Emitting deprecation messages
> in the API entry points tied to user data is a clear purpose, not
> open to abuse. Recording the difference between user set & internally
> set against the object instance persistently is an open ended purpose
> and based on what we've seen in QEMU in the past, that is highly likely
> to be mis-used.
>
> The idea of supporting deprecations on properties is definitely
> something we should do, but I really dn't want to see that expressed
> via the 'user set' mechanism from this series.
Thank you for your explanation. In practice, as the alternative to
USER_SET, I understand we identify the specific API entry points (including
object_set_properties_from_qdict and others) and trigger the warning
directly within those functions / code path, may I ask if this
understanding is right?
The current API entry points are somewhat fragmented; perhaps we should
consider whether further unification is possible.
Regards,
Zhao
next prev parent reply other threads:[~2026-03-09 13:11 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 3:23 [PATCH v2 00/21] qom: introduce property flags to track external user input Zhao Liu
2026-02-10 3:23 ` [PATCH v2 01/21] qom/object: use BIT macro for ObjectPropertyFlags Zhao Liu
2026-03-20 9:53 ` Thomas Huth
2026-02-10 3:23 ` [PATCH v2 02/21] qom/object: cache ObjectPropertyFlags in ObjectProperty Zhao Liu
2026-03-20 9:53 ` Thomas Huth
2026-02-10 3:23 ` [PATCH v2 03/21] qom/object: factor out object_class_property_try_add() Zhao Liu
2026-02-10 14:41 ` BALATON Zoltan
2026-02-11 7:14 ` Zhao Liu
2026-02-10 3:23 ` [PATCH v2 04/21] qom/object: add flags argument in object_{class_}property_try_add() Zhao Liu
2026-02-10 3:23 ` [PATCH v2 05/21] qom/object: rename object_{class_}property_try_add() to object_{class_}property_add_full() Zhao Liu
2026-02-10 3:23 ` [PATCH v2 06/21] qom/object: add helpers to set/get/clear property flags Zhao Liu
2026-02-10 3:23 ` [PATCH v2 07/21] qom/object: introduce user interaction flags for properties Zhao Liu
2026-02-10 9:49 ` Daniel P. Berrangé
2026-02-10 9:58 ` Daniel P. Berrangé
2026-02-11 8:19 ` Zhao Liu
2026-02-10 14:44 ` BALATON Zoltan
2026-02-11 7:22 ` Zhao Liu
2026-02-10 3:23 ` [PATCH v2 08/21] qom/object: add from_user argument in object_property_parse() Zhao Liu
2026-02-10 3:23 ` [PATCH v2 09/21] qom/object: mark global property set from CLI as USER_SET Zhao Liu
2026-02-10 3:23 ` [PATCH v2 10/21] qom/qom-hmp-cmd: mark properties set from HMP (non-JSON) "qom-set" " Zhao Liu
2026-02-10 3:23 ` [PATCH v2 11/21] qom/qom-qmp-cmd: mark properties set from QMP/HMP (JSON) " Zhao Liu
2026-02-10 3:23 ` [PATCH v2 12/21] qom/object_interfaces: mark properties set from qdict & keyval " Zhao Liu
2026-02-10 3:23 ` [PATCH v2 13/21] system/vl: mark property set in object_parse_property_opt() " Zhao Liu
2026-02-10 3:23 ` [PATCH v2 14/21] hw/core/qdev-properties: allow qdev properties accept flags Zhao Liu
2026-02-10 9:41 ` Peter Krempa
2026-02-11 7:10 ` Zhao Liu
2026-02-10 9:56 ` Daniel P. Berrangé
2026-02-11 7:30 ` Zhao Liu
2026-02-11 16:58 ` Daniel P. Berrangé
2026-02-12 15:25 ` Zhao Liu
2026-02-12 15:42 ` Daniel P. Berrangé
2026-03-09 13:34 ` Zhao Liu [this message]
2026-02-18 9:51 ` Igor Mammedov
2026-03-06 9:14 ` Markus Armbruster
2026-03-06 9:19 ` Daniel P. Berrangé
2026-03-06 9:30 ` Markus Armbruster
2026-03-09 13:52 ` Zhao Liu
2026-02-10 3:23 ` [PATCH v2 15/21] target/i386: deprecate fill-mtrr-mask property Zhao Liu
2026-02-10 3:23 ` [PATCH v2 16/21] target/i386: deprecate cpuid-0xb property Zhao Liu
2026-02-10 3:23 ` [PATCH v2 17/21] hw/intc/ioapic: deprecate version property Zhao Liu
2026-02-10 3:23 ` [PATCH v2 18/21] target/i386: mark x-consistent-cache property as internal-only Zhao Liu
2026-02-10 3:23 ` [PATCH v2 19/21] target/i386: remove redundant validation for lbr-fmt property Zhao Liu
2026-03-13 22:34 ` Chen, Zide
2026-02-10 3:23 ` [PATCH v2 20/21] target/i386: detect user provided lbr-fmt via property flag Zhao Liu
2026-03-13 22:36 ` Chen, Zide
2026-02-10 3:23 ` [PATCH v2 21/21] hw/core/qdev-properties: support valid default value for DEFINE_PROP_UINT64_CHECKMASK Zhao Liu
2026-03-13 22:36 ` Chen, Zide
2026-02-10 10:12 ` [PATCH v2 00/21] qom: introduce property flags to track external user input Daniel P. Berrangé
2026-02-10 10:44 ` Michael S. Tsirkin
2026-02-10 11:00 ` Daniel P. Berrangé
2026-02-10 15:00 ` BALATON Zoltan
2026-02-10 15:28 ` Zhao Liu
2026-02-10 15:16 ` BALATON Zoltan
2026-02-11 7:24 ` Zhao Liu
2026-02-11 11:28 ` BALATON Zoltan
2026-02-12 15:31 ` Zhao Liu
2026-02-12 15:56 ` BALATON Zoltan
2026-02-10 15:41 ` Daniel P. Berrangé
2026-02-11 7:06 ` Zhao Liu
2026-02-11 11:18 ` Daniel P. Berrangé
2026-03-11 13:05 ` Markus Armbruster
2026-03-11 13:14 ` Daniel P. Berrangé
2026-03-11 13:38 ` Peter Krempa
2026-03-16 15:43 ` Markus Armbruster
2026-03-16 16:05 ` BALATON Zoltan
2026-03-16 18:00 ` Markus Armbruster
2026-03-20 10:09 ` Daniel P. Berrangé
2026-03-23 15:37 ` Kevin Wolf
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=aa7Mckq/8cgwZwkB@intel.com \
--to=zhao1.liu@intel.com \
--cc=armbru@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=berrange@redhat.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=devel@lists.libvirt.org \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=mark.caveayland@nutanix.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=zide.chen@intel.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.