From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Mark Cave-Ayland" <mark.caveayland@nutanix.com>,
pbonzini@redhat.com, richard.henderson@linaro.org,
mst@redhat.com, mtosatti@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 8/9] hw/i386/pc_sysfw.c: convert pflash0 and pflash1 object props to class props
Date: Fri, 10 Jul 2026 16:00:55 +0200 [thread overview]
Message-ID: <87v7anx7u0.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_isBMYU8mEZV-sjbiePHLDqERiczkoPP6xw4i4UYm5pw@mail.gmail.com> (Peter Maydell's message of "Wed, 8 Jul 2026 14:27:44 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Wed, 8 Jul 2026 at 13:57, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> Daniel P. Berrangé <berrange@redhat.com> writes:
>>
>> > On Wed, Jul 08, 2026 at 02:50:54PM +0200, Markus Armbruster wrote:
>> >> > Something would need to validate that instantiating a machine type
>> >> > for help usage won't trip over any edge cases. Could be done with
>> >> > unit tests.
>> >>
>> >> tests/qtest/device-introspect-test.c covers this for devices.
>> >
>> > Ah, good, I was misled by its name into thinking it was only devices,
>> > not machine types too.
>>
>> Misunderstanding: it does cover it for devices, and only for devices.
>
> Does Marc-André's recent qom-tests test cover the machines? It
> does an instantiate/get props/unref cycle for all non-abstract
> QOM types, which ought to include the machines.
I guess you mean commit f741225073 (qtest: add "qom-tests" command,
2026-04-24). Looking at the code... yes, that should cover machines.
> A while back I had a look at moving Machine to be a subclass
> of Device, incidentally -- that would let us have machine
> reset not be a weird special case, allow separating machine
> init from realize, and make machines be more like SoC objects
> (which they resemble a lot in being "creates, configures
> and wires up a load of other devices").
Makes sense to me.
> I forget where I
> got to in that, though.
Been there, done that *sigh*.
next prev parent reply other threads:[~2026-07-10 14:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 9:07 [PATCH 0/9] hw/i386: convert object props to class props Mark Cave-Ayland
2026-07-03 9:07 ` [PATCH 1/9] qom/object.c: introduce object_alias_get_targetp() lookup function Mark Cave-Ayland
2026-07-03 9:07 ` [PATCH 2/9] qom/object.c: introduce object_class_property_add_alias() Mark Cave-Ayland
2026-07-03 9:07 ` [PATCH 3/9] qom/object.c: introduce object_property_set_alias() function Mark Cave-Ayland
2026-07-03 9:07 ` [PATCH 4/9] hw/i386/pc.c: convert pcspk-audiodev object prop to a class prop Mark Cave-Ayland
2026-07-03 9:07 ` [PATCH 5/9] hw/rtc/mc146818rtc.c: convert date from object prop to " Mark Cave-Ayland
2026-07-06 7:15 ` Philippe Mathieu-Daudé
2026-07-03 9:07 ` [PATCH 6/9] hw/i386/pc.c: convert rtc-time object prop to a " Mark Cave-Ayland
2026-07-07 16:58 ` Daniel P. Berrangé
2026-07-03 9:08 ` [PATCH 7/9] hw/i386/pc.c: convert PC_MACHINE_ACPI_DEVICE_PROP from object prop to " Mark Cave-Ayland
2026-07-07 16:48 ` Daniel P. Berrangé
2026-07-03 9:08 ` [PATCH 8/9] hw/i386/pc_sysfw.c: convert pflash0 and pflash1 object props to class props Mark Cave-Ayland
2026-07-07 16:58 ` Daniel P. Berrangé
2026-07-08 9:40 ` Mark Cave-Ayland
2026-07-08 9:56 ` Daniel P. Berrangé
2026-07-08 10:16 ` Peter Maydell
2026-07-08 10:24 ` Daniel P. Berrangé
2026-07-08 11:21 ` Markus Armbruster
2026-07-08 11:28 ` Daniel P. Berrangé
2026-07-08 12:50 ` Markus Armbruster
2026-07-08 12:53 ` Daniel P. Berrangé
2026-07-08 12:57 ` Markus Armbruster
2026-07-08 13:27 ` Peter Maydell
2026-07-10 14:00 ` Markus Armbruster [this message]
2026-07-08 10:28 ` Mark Cave-Ayland
2026-07-03 9:08 ` [PATCH 9/9] hw/i386/sgx-epc.c: convert SGX_EPC_SIZE_PROP object prop to class prop Mark Cave-Ayland
2026-07-07 16:54 ` Daniel P. Berrangé
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=87v7anx7u0.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=mark.caveayland@nutanix.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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.