From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v4 00/10] qom: misc cleanups / fixes
Date: Tue, 12 May 2026 13:29:48 +0100 [thread overview]
Message-ID: <20260512122958.788097-1-berrange@redhat.com> (raw)
The overall theme of this patch is to move some logic out of
object_interfaces.c into object.c, since it is not tied to
the user creatable interface.
Changed in v4:
- Invoke va_end on the correct variable
- Fix commit message typo
Changed in v3:
- Fix parent/child mixup in trace event param names
- Make QDict const in new constructors
Changed in v2:
- Ensure object creation always triggers module loading
- Remove redundant NULL check in trace event
- Remove double #include line
Daniel P. Berrangé (10):
qom: add trace events for object/property lifecycle
qom: validate ID format when creating objects
qom: make errp last param in methods taking va_list
qom: shorten name of object_set_properties_from_keyval
qom: have object_set_props_keyval return bool
qom: move object_set_prop_keyval into object.c
qom: add object_new_with_props_from_qdict
qom: fix ability to create objects without a parent
qom: allow object_new_with_prop* to trigger module loading
qom: drop user_creatable_add_type method
authz/listfile.c | 4 +-
include/qom/object.h | 121 ++++++++++++++---
include/qom/object_interfaces.h | 18 ---
qom/object.c | 230 ++++++++++++++++++++++++++++----
qom/object_interfaces.c | 101 +-------------
qom/trace-events | 12 +-
system/qdev-monitor.c | 4 +-
system/vl.c | 7 +-
tests/unit/check-qom-proplist.c | 97 +++++++++++---
9 files changed, 409 insertions(+), 185 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-12 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:29 Daniel P. Berrangé [this message]
2026-05-12 12:29 ` [PATCH v4 01/10] qom: add trace events for object/property lifecycle Daniel P. Berrangé
2026-05-13 6:16 ` Philippe Mathieu-Daudé
2026-05-13 14:33 ` Philippe Mathieu-Daudé
2026-05-12 12:29 ` [PATCH v4 02/10] qom: validate ID format when creating objects Daniel P. Berrangé
2026-05-13 14:35 ` Philippe Mathieu-Daudé
2026-05-12 12:29 ` [PATCH v4 03/10] qom: make errp last param in methods taking va_list Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 04/10] qom: shorten name of object_set_properties_from_keyval Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 05/10] qom: have object_set_props_keyval return bool Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 06/10] qom: move object_set_prop_keyval into object.c Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 07/10] qom: add object_new_with_props_from_qdict Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 08/10] qom: fix ability to create objects without a parent Daniel P. Berrangé
2026-05-13 14:35 ` Philippe Mathieu-Daudé
2026-05-12 12:29 ` [PATCH v4 09/10] qom: allow object_new_with_prop* to trigger module loading Daniel P. Berrangé
2026-05-12 12:29 ` [PATCH v4 10/10] qom: drop user_creatable_add_type method Daniel P. Berrangé
2026-05-13 14:35 ` Philippe Mathieu-Daudé
2026-05-12 13:12 ` [PATCH v4 00/10] qom: misc cleanups / fixes marcandre.lureau
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=20260512122958.788097-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox