From: David Hildenbrand <david@redhat.com>
To: Collin Walling <walling@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: thuth@redhat.com, wangyanan55@huawei.com, philmd@linaro.org,
marcel.apfelbaum@gmail.com, eduardo@habkost.net,
armbru@redhat.com
Subject: Re: [PATCH v3 1/2] target/s390x: report deprecated-props in cpu-model-expansion reply
Date: Fri, 26 Apr 2024 19:45:49 +0200 [thread overview]
Message-ID: <c5d459eb-c38f-4e8c-a1c3-ba47584e5b2a@redhat.com> (raw)
In-Reply-To: <60cd9494-fe97-4134-a16b-026e14186eed@redhat.com>
On 26.04.24 19:44, David Hildenbrand wrote:
> On 24.04.24 23:56, Collin Walling wrote:
>> Retain a list of deprecated features disjoint from any particular
>> CPU model. A query-cpu-model-expansion reply will now provide a list of
>> properties (i.e. features) that are flagged as deprecated. Example:
>>
>> {
>> "return": {
>> "model": {
>> "name": "z14.2-base",
>> "deprecated-props": [
>> "bpb",
>> "csske"
>> ],
>> "props": {
>> "pfmfi": false,
>> "exrl": true,
>> ...a lot more props...
>> "skey": false,
>> "vxpdeh2": false
>> }
>> }
>> }
>> }
>>
>> It is recommended that s390 guests operate with these features
>> explicitly disabled to ensure compatability with future hardware.
>
> Likely you should only report features that are applicable to a model.
> that is, if it's part of the full_feat.
>
> Otherwise, the caller might simply want do set all features to "false",
> and we'd fail setting a feature that is unknown to a specific CPU
> generation.
>
> That is, you would AND the bitmap with the full_feat of the underlying
> CPU definition.
Refreshing my memory, I think we can just clear any CPU features. We
only bail out when setting them!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-04-26 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 21:56 [PATCH v3 0/2] query-cpu-model-expansion: report deprecated features Collin Walling
2024-04-24 21:56 ` [PATCH v3 1/2] target/s390x: report deprecated-props in cpu-model-expansion reply Collin Walling
2024-04-26 8:42 ` Markus Armbruster
2024-04-26 17:35 ` Collin Walling
2024-04-26 20:11 ` Collin Walling
2024-04-26 17:44 ` David Hildenbrand
2024-04-26 17:45 ` David Hildenbrand [this message]
2024-04-26 19:28 ` Collin Walling
2024-04-24 21:56 ` [PATCH v3 2/2] target/s390x: flag te and cte as deprecated Collin Walling
2024-04-24 22:05 ` [PATCH v3 0/2] query-cpu-model-expansion: report deprecated features 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=c5d459eb-c38f-4e8c-a1c3-ba47584e5b2a@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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).