From: Markus Armbruster <armbru@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Michael Roth" <michael.roth@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
berrange@redhat.com, "Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v2 08/12] qapi: Make CpuModelExpansionInfo::deprecated-props optional and generic
Date: Mon, 19 May 2025 08:18:52 +0200 [thread overview]
Message-ID: <87a579jf77.fsf@pond.sub.org> (raw)
In-Reply-To: <20250515172732.3992504-9-pierrick.bouvier@linaro.org> (Pierrick Bouvier's message of "Thu, 15 May 2025 10:27:28 -0700")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> From: Philippe Mathieu-Daudé <philmd@linaro.org>
>
> We'd like to have some unified QAPI schema. Having a structure field
> conditional to a target being built in is not very practical.
>
> While @deprecated-props is only used by s390x target, it is generic
> enough and could be used by other targets (assuming we expand
> CpuModelExpansionType enum values).
>
> Let's always include this field, regardless of the target, but
> make it optional.
Let's add:
This is not a compatibility break only because the field remains
present always on S390x.
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> qapi/machine-target.json | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/qapi/machine-target.json b/qapi/machine-target.json
> index 426ce4ee82d..e153291a7fc 100644
> --- a/qapi/machine-target.json
> +++ b/qapi/machine-target.json
> @@ -244,19 +244,18 @@
> #
> # @model: the expanded CpuModelInfo.
> #
> -# @deprecated-props: a list of properties that are flagged as
> +# @deprecated-props: an optional list of properties that are flagged as
> # deprecated by the CPU vendor. The list depends on the
> # CpuModelExpansionType: "static" properties are a subset of the
> # enabled-properties for the expanded model; "full" properties are
> # a set of properties that are deprecated across all models for
> -# the architecture. (since: 9.1).
> +# the architecture. (since: 10.1 -- since 9.1 on s390x --).
> #
> # Since: 2.8
> ##
> { 'struct': 'CpuModelExpansionInfo',
> 'data': { 'model': 'CpuModelInfo',
> - 'deprecated-props' : { 'type': ['str'],
> - 'if': 'TARGET_S390X' } },
> + '*deprecated-props' : { 'type': ['str'] } },
[Copied from review of prior posts]
Make this
'*deprecated-props' : ['str'] },
please.
When I see "optional array", I wonder about the difference between
"absent" and "present and empty". The doc comment doesn't quite explain
it. I figure "present and empty" means empty, while "absent" means we
don't know / not implemented.
Is the difference useful?
Daniel doubts it is.
Philippe is happy to implement either variant.
> 'if': { 'any': [ 'TARGET_S390X',
> 'TARGET_I386',
> 'TARGET_ARM',
Note the patch doesn't touch any of the qmp_query_cpu_model_expansion().
The S390x version continues to set @deprecated_props always. The others
continue not to set it.
next prev parent reply other threads:[~2025-05-19 6:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 17:27 [PATCH v2 00/12] qapi: remove all TARGET_* conditionals from the schema Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 01/12] qapi: expose rtc-reset-reinjection command unconditionally Pierrick Bouvier
2025-05-17 8:21 ` Markus Armbruster
2025-05-17 19:39 ` Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 02/12] qapi: expand docs for SEV commands Pierrick Bouvier
2025-05-19 5:57 ` Markus Armbruster
2025-05-21 19:21 ` Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 03/12] qapi: make SEV commands unconditionally available Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 04/12] qapi: expose query-gic-capability command unconditionally Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 05/12] qapi: make SGX commands unconditionally available Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 06/12] qapi: make Xen event " Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 07/12] qapi: remove the misc-target.json file Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 08/12] qapi: Make CpuModelExpansionInfo::deprecated-props optional and generic Pierrick Bouvier
2025-05-19 6:18 ` Markus Armbruster [this message]
2025-05-21 19:22 ` Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 09/12] qapi: make most CPU commands unconditionally available Pierrick Bouvier
2025-05-17 6:00 ` Markus Armbruster
2025-05-17 19:41 ` Pierrick Bouvier
2025-05-19 6:29 ` Markus Armbruster
2025-05-21 19:29 ` Pierrick Bouvier
2025-05-22 5:12 ` Markus Armbruster
2025-05-22 18:45 ` Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 10/12] qapi: make s390x specific " Pierrick Bouvier
2025-05-15 17:27 ` [PATCH v2 11/12] qapi: remove qapi_specific_outputs from meson.build Pierrick Bouvier
2025-05-19 8:50 ` Markus Armbruster
2025-05-15 17:27 ` [PATCH v2 12/12] qapi: make all generated files common Pierrick Bouvier
2025-05-19 9:14 ` Markus Armbruster
2025-05-21 22:41 ` [PATCH v2 00/12] qapi: remove all TARGET_* conditionals from the schema Pierrick Bouvier
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=87a579jf77.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=michael.roth@amd.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 \
/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.