From: Rob Herring <robh@kernel.org>
To: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Radoslaw Biernacki" <rad@semihalf.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH v2] hw/arm: add versioning to sbsa-ref machine DT
Date: Tue, 17 May 2022 08:27:06 -0500 [thread overview]
Message-ID: <CAL_JsqJirHpxC-QXDZUKbJUTgYpac3KyTh7r3v0frWg26F3rzQ@mail.gmail.com> (raw)
In-Reply-To: <20220505113947.75714-1-quic_llindhol@quicinc.com>
On Thu, May 5, 2022 at 6:41 AM Leif Lindholm <quic_llindhol@quicinc.com> wrote:
>
> The sbsa-ref machine is continuously evolving. Some of the changes we
> want to make in the near future, to align with real components (e.g.
> the GIC-700), will break compatibility for existing firmware.
>
> Introduce two new properties to the DT generated on machine generation:
> - machine-version-major
> To be incremented when a platform change makes the machine
> incompatible with existing firmware.
> - machine-version-minor
> To be incremented when functionality is added to the machine
> without causing incompatibility with existing firmware.
> to be reset to 0 when machine-version-major is incremented.
Where's the binding documentation for this?
We already have a way to version DTs and that's with compatible. I'm
not completely opposed to a version number though, but I am opposed to
it not being common. We've rejected vendors (QCom in fact) doing their
own thing here.
> This versioning scheme is *neither*:
> - A QEMU versioned machine type; a given version of QEMU will emulate
> a given version of the platform.
> - A reflection of level of SBSA (now SystemReady SR) support provided.
FYI, it's planned to certify the virt machine for SR-IR which will
include DT schema validation. Undocumented properties are a problem
for that.
> The version will increment on guest-visible functional changes only,
> akin to a revision ID register found on a physical platform.
>
> These properties are both introduced with the value 0.
> (Hence, a machine where the DT is lacking these nodes is equivalent
> to version 0.0.)
>
> Signed-off-by: Leif Lindholm <quic_llindhol@quicinc.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Radoslaw Biernacki <rad@semihalf.com>
> Cc: Cédric Le Goater <clg@kaod.org>
> ---
>
> Changes since v1:
> - More detail added to commit message.
> - Verbose comment added adjacent to code additions.
>
> hw/arm/sbsa-ref.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/hw/arm/sbsa-ref.c b/hw/arm/sbsa-ref.c
> index 2387401963..d0c25ddfcf 100644
> --- a/hw/arm/sbsa-ref.c
> +++ b/hw/arm/sbsa-ref.c
> @@ -190,6 +190,20 @@ static void create_fdt(SBSAMachineState *sms)
> qemu_fdt_setprop_cell(fdt, "/", "#address-cells", 0x2);
> qemu_fdt_setprop_cell(fdt, "/", "#size-cells", 0x2);
>
> + /*
> + * This versioning scheme is for informing platform fw only. It is neither:
> + * - A QEMU versioned machine type; a given version of QEMU will emulate
> + * a given version of the platform.
> + * - A reflection of level of SBSA (now SystemReady SR) support provided.
> + *
> + * machine-version-major: updated when changes breaking fw compatibility
> + * are introduced.
> + * machine-version-minor: updated when features are added that don't break
> + * fw compatibility.
> + */
> + qemu_fdt_setprop_cell(fdt, "/", "machine-version-major", 0);
> + qemu_fdt_setprop_cell(fdt, "/", "machine-version-minor", 0);
> +
> if (ms->numa_state->have_numa_distance) {
> int size = nb_numa_nodes * nb_numa_nodes * 3 * sizeof(uint32_t);
> uint32_t *matrix = g_malloc0(size);
> --
> 2.30.2
>
>
next prev parent reply other threads:[~2022-05-17 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 11:39 [PATCH v2] hw/arm: add versioning to sbsa-ref machine DT Leif Lindholm
2022-05-09 9:37 ` Peter Maydell
2022-05-17 13:27 ` Rob Herring [this message]
2022-05-17 16:50 ` Peter Maydell
2022-05-17 20:30 ` Rob Herring
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=CAL_JsqJirHpxC-QXDZUKbJUTgYpac3KyTh7r3v0frWg26F3rzQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=clg@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.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).