From: David Hildenbrand <david@redhat.com>
To: Collin Walling <walling@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: eduardo@habkost.net, marcel.apfelbaum@gmail.com,
philmd@linaro.org, wangyanan55@huawei.com, eblake@redhat.com,
armbru@redhat.com, richard.henderson@linaro.org,
iii@linux.ibm.com, thuth@redhat.com
Subject: Re: [PATCH v1 1/2] target/s390x: introduce "host-recommended" option for model expansion
Date: Tue, 12 Sep 2023 08:57:27 +0200 [thread overview]
Message-ID: <bbf67ab2-2868-7c3a-0e8e-8f53fd62c1fb@redhat.com> (raw)
In-Reply-To: <20230911205232.71735-1-walling@linux.ibm.com>
On 11.09.23 22:52, Collin Walling wrote:
Patch subject is wrong (should contain "static-recommended")
> Newer S390 machines may drop support for features completely, rendering
> guests operating with older CPU models incapable of running on said
> machines. A manual effort to disable certain CPU features would be
> required.
>
> To alleviate this issue, a list of "deprecated" features are now
> retained within QEMU, and a new "static-recommended" CPU model expansion
> type has been created to allow a query of the host-model with deprecated
> features explicitly disabled.
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> ---
> qapi/machine-target.json | 8 +++++++-
> target/s390x/cpu_features.c | 14 ++++++++++++++
> target/s390x/cpu_features.h | 1 +
> target/s390x/cpu_models_sysemu.c | 26 +++++++++++++++++++++-----
> 4 files changed, 43 insertions(+), 6 deletions(-)
>
> diff --git a/qapi/machine-target.json b/qapi/machine-target.json
> index f0a6b72414..4dc891809d 100644
> --- a/qapi/machine-target.json
> +++ b/qapi/machine-target.json
> @@ -42,6 +42,12 @@
> # to be migration-safe, but allows tooling to get an insight and
> # work with model details.
> #
> +# @static-recommended: Expand to a static CPU model with property
> +# changes suggested by the architecture. This is useful for
> +# expanding a CPU model expected to operate in mixed
> +# CPU-generation environments. The @static-recommended CPU
> +# models are migration-safe.
> +#
Can we instead make this a new parameter for query-cpu-model-expansion
("no-deprecated-features" ? ), that properly gets rejected from other
archs when not supported?
[...]
> /* convert S390CPUDef into a static CpuModelInfo */
> static void cpu_info_from_model(CpuModelInfo *info, const S390CPUModel *model,
> - bool delta_changes)
> + bool delta_changes, bool disable_dep_feats)
"dep" can be misleading ("depended")
"no_deprecated_feat" ?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-12 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 20:52 [PATCH v1 1/2] target/s390x: introduce "host-recommended" option for model expansion Collin Walling
2023-09-11 20:52 ` [PATCH v1 2/2] target/s390x: flag te and cte as deprecated Collin Walling
2023-09-12 6:59 ` David Hildenbrand
2023-09-12 6:57 ` David Hildenbrand [this message]
2023-09-14 19:28 ` [PATCH v1 1/2] target/s390x: introduce "host-recommended" option for model expansion Collin Walling
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=bbf67ab2-2868-7c3a-0e8e-8f53fd62c1fb@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=iii@linux.ibm.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
--cc=wangyanan55@huawei.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).