From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
kvm@vger.kernel.org, "Zhao Liu" <zhao1.liu@intel.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Peter Xu" <peterx@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH 4/9] hw/qdev: Introduce DeviceClass::[un]wire() handlers
Date: Tue, 28 Jan 2025 12:52:39 -0800 [thread overview]
Message-ID: <b7646baf-a07d-4ded-804c-6809173c1f6b@linaro.org> (raw)
In-Reply-To: <20250128142152.9889-5-philmd@linaro.org>
On 1/28/25 06:21, Philippe Mathieu-Daudé wrote:
> We are trying to understand what means "a qdev is realized".
> One explanation was "the device is guest visible"; however
> many devices are realized before being mapped, thus are not
> "guest visible". Some devices map / wire their IRQs before
> being realized (such ISA devices). There is a need for devices
> to be "automatically" mapped/wired (see [2]) such CLI-created
> devices, but this apply generically to dynamic machines.
>
> Currently the device creation steps are expected to roughly be:
>
> (external use) (QDev core) (Device Impl)
> ~~~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~
>
> INIT enter
> ----->
> +----------------------+
> | Allocate state |
> +----------------------+
> ----->
> +---------------------+
> | INIT children |
> | |
> | Alias children properties
> | |
> | Expose properties |
> INIT exit +---------------------+
> <-----------------------------------
> +----------------+
> | set properties |
> | |
> | set ClkIn |
> +----------------+ REALIZE enter
> ---------------------------------->
> +----------------------+
> | Use config properties|
> | |
> | Realize children |
> | |
> | Init GPIOs/IRQs |
> | |
> | Init MemoryRegions |
> +----------------------+
> REALIZE exit
> <----------------------------------- ---- "realized" / "guest visible"
> +-----------------+
> | Explicit wiring:|
> | IRQs |
> | I/O / Mem |
> | ClkOut |
> +-----------------+ RESET enter
> --------------------------------->
> +----------------------+
> | Reset default values |
> +----------------------+
>
> But as mentioned, various devices "wire" parts before they exit
> the "realize" step.
> In order to clarify, I'm trying to enforce what can be done
> *before* and *after* realization.
>
> *after* a device is expected to be stable (no more configurable)
> and fully usable.
>
> To be able to use internal/auto wiring (such ISA devices) and
> keep the current external/explicit wiring, I propose to add an
> extra "internal wiring" step, happening after the REALIZE step
> as:
>
> (external use) (QDev core) (Device Impl)
> ~~~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~
>
> INIT enter
> ----->
> +----------------------+
> | Allocate state |
> +----------------------+
> ----->
> +---------------------+
> | INIT children |
> | |
> | Alias children properties
> | |
> | Expose properties |
> INIT exit +---------------------+
> <-----------------------------------
> +----------------+
> | set properties |
> | |
> | set ClkIn |
> +----------------+ REALIZE enter
> ---------------------------------->
> +----------------------+
> | Use config properties|
> | |
> | Realize children |
> | |
> | Init GPIOs/IRQs |
> | |
> | Init MemoryRegions |
> +----------------------+
> REALIZE exit <---
> +----------------------+
> | Internal auto wiring |
> | IRQs | (i.e. ISA bus)
> | I/O / Mem |
> | ClkOut |
> +----------------------+
> <--- ---- "realized"
> +-----------------+
> | External wiring:|
> | IRQs |
> | I/O / Mem |
> | ClkOut |
> +-----------------+ RESET enter ---- "guest visible"
> --------------------------------->
> +----------------------+
> | Reset default values |
> +----------------------+
>
> The "realized" point is not changed. "guest visible" concept only
> occurs *after* wiring, just before the reset phase.
>
> This change introduces the DeviceClass::wire handler within qdev
> core realization code.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/hw/qdev-core.h | 7 +++++++
> hw/core/qdev.c | 20 +++++++++++++++++++-
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/include/hw/qdev-core.h b/include/hw/qdev-core.h
> index 530f3da7021..021bb7afdc0 100644
> --- a/include/hw/qdev-core.h
> +++ b/include/hw/qdev-core.h
> @@ -102,7 +102,12 @@ typedef int (*DeviceSyncConfig)(DeviceState *dev, Error **errp);
> * @props: Properties accessing state fields.
> * @realize: Callback function invoked when the #DeviceState:realized
> * property is changed to %true.
> + * @wire: Callback function called after @realize to connect IRQs,
> + * clocks and map memories. Can not fail.
> + * @unwire: Callback function to undo @wire. Called before @unrealize.
> + * Can not fail.
> * @unrealize: Callback function invoked when the #DeviceState:realized
> + * property is changed to %false. Can not fail.
> * property is changed to %false.
> * @sync_config: Callback function invoked when QMP command device-sync-config
> * is called. Should synchronize device configuration from host to guest part
> @@ -171,6 +176,8 @@ struct DeviceClass {
> */
> DeviceReset legacy_reset;
> DeviceRealize realize;
> + void (*wire)(DeviceState *dev);
> + void (*unwire)(DeviceState *dev);
> DeviceUnrealize unrealize;
> DeviceSyncConfig sync_config;
>
> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
> index 82bbdcb654e..38449255365 100644
> --- a/hw/core/qdev.c
> +++ b/hw/core/qdev.c
> @@ -554,6 +554,15 @@ static void device_set_realized(Object *obj, bool value, Error **errp)
> }
> }
>
> + if (dc->wire) {
> + if (!dc->unwire) {
> + warn_report_once("wire() without unwire() for type '%s'",
> + object_get_typename(OBJECT(dev)));
> + }
> + dc->wire(dev);
> + }
> +
> + /* At this point the device is "guest visible". */
> qatomic_store_release(&dev->realized, value);
>
> } else if (!value && dev->realized) {
> @@ -573,6 +582,15 @@ static void device_set_realized(Object *obj, bool value, Error **errp)
> */
> smp_wmb();
>
> + if (dc->unwire) {
> + if (!dc->wire) {
> + error_report("disconnect() without connect() for type '%s'",
> + object_get_typename(OBJECT(dev)));
> + abort();
> + }
> + dc->unwire(dev);
> + }
Mismatched error messages (wire vs connect).
But, really, just check both directions properly at startup.
There's probably lots of places where devices are never unrealized.
Otherwise, this seems sane, having a kind of post_init on the realize path, running after
all superclass realization is done.
r~
next prev parent reply other threads:[~2025-01-28 20:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 14:21 [RFC PATCH 0/9] accel: Only include qdev-realized vCPUs in global &cpus_queue Philippe Mathieu-Daudé
2025-01-28 14:21 ` [RFC PATCH 1/9] accel/tcg: Simplify use of &first_cpu in rr_cpu_thread_fn() Philippe Mathieu-Daudé
2025-01-28 19:44 ` Richard Henderson
2025-01-28 14:21 ` [RFC PATCH 2/9] accel/tcg: Invalidate TB jump cache with global vCPU queue locked Philippe Mathieu-Daudé
2025-01-28 20:05 ` Richard Henderson
2025-01-28 14:21 ` [RFC PATCH 3/9] cpus: Remove cpu from global queue after UNREALIZE completed Philippe Mathieu-Daudé
2025-01-28 20:08 ` Richard Henderson
2025-01-28 14:21 ` [RFC PATCH 4/9] hw/qdev: Introduce DeviceClass::[un]wire() handlers Philippe Mathieu-Daudé
2025-01-28 20:52 ` Richard Henderson [this message]
2025-02-04 13:39 ` Igor Mammedov
2025-01-28 14:21 ` [PATCH 5/9] cpus: Add DeviceClass::[un]wire() stubs Philippe Mathieu-Daudé
2025-01-28 20:53 ` Richard Henderson
2025-01-28 14:21 ` [PATCH 6/9] cpus: Call hotplug handlers in DeviceWire() Philippe Mathieu-Daudé
2025-01-28 20:53 ` Richard Henderson
2025-01-28 14:21 ` [RFC PATCH 7/9] cpus: Only expose REALIZED vCPUs to global &cpus_queue Philippe Mathieu-Daudé
2025-01-28 20:53 ` Richard Henderson
2025-01-28 20:55 ` Richard Henderson
2025-01-28 14:21 ` [PATCH 8/9] accel/kvm: Assert vCPU is created when calling kvm_dirty_ring_reap*() Philippe Mathieu-Daudé
2025-01-28 20:57 ` Richard Henderson
2025-01-28 14:21 ` [PATCH 9/9] accel/kvm: Remove unreachable assertion in kvm_dirty_ring_reap*() Philippe Mathieu-Daudé
2025-01-28 20:58 ` Richard Henderson
2025-02-07 15:45 ` [RFC PATCH 0/9] accel: Only include qdev-realized vCPUs in global &cpus_queue Igor Mammedov
2025-02-09 18:02 ` Philippe Mathieu-Daudé
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=b7646baf-a07d-4ded-804c-6809173c1f6b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=harshpb@linux.ibm.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).