From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
qemu-s390x@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, Ilya Leoshkevich <iii@linux.ibm.com>,
Ani Sinha <anisinha@redhat.com>
Subject: Re: [PATCH] target/s390x: Add a CONFIG switch to disable legacy CPUs
Date: Fri, 14 Jun 2024 10:24:29 +0200 [thread overview]
Message-ID: <c752752a-c45c-4428-948f-b27c18510007@redhat.com> (raw)
In-Reply-To: <dd562095-f104-48d8-abe9-9b22b53b8743@linux.ibm.com>
On 14/06/2024 10.17, Christian Borntraeger wrote:
>
>
> Am 14.06.24 um 09:15 schrieb Thomas Huth:
>> On 14/06/2024 08.07, Christian Borntraeger wrote:
>>>
>>>
>>> Am 13.06.24 um 19:07 schrieb Thomas Huth:
>>>> Old CPU models are not officially supported anymore by IBM, and for
>>>> downstream builds of QEMU, we would like to be able to disable these
>>>> CPUs in the build. Thus add a CONFIG switch that can be used to
>>>> disable these CPUs (and old machine types that use them by default).
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>> If you're interested, the PDF that can be downloaded from
>>>> https://www.ibm.com/support/pages/ibm-mainframe-life-cycle-history
>>>> shows the supported CPUs in a nice diagram
>>>
>>> z13 is still supported so the patch needs to be fixed at least.
>>
>> Oh, drat, I misread the diagram, indeed. 'should have looked at the table
>> instead :-/
>>
>>> Furthermore, z14 has the IBC/VAL cabability to behave like a z13,
>>> same for z15. (we do support VAL to N-2)
>>
>> Hmm, so if z13 is still supported, and also has the possibility to do N-2,
>> I assume the z114/196 and z12 should still be considered as non-legacy, too?
>
> Yes. z9 and older is no longer relevant (only for people that collect old
> HW) but the upstream kernel has an minimum requirement for z10 so maybe we
> still want to support that for testing purposes.
Ok, fair point, kernel support is a good hint, too.
> For upstream I prefer to keep the full list but I would be ok to hide those
> ancient things behind a config switch.
That's what this patch is trying to do - by default, all CPUs are still
enabled, you have actively disable the switch to get rid of the old ones.
Thomas
prev parent reply other threads:[~2024-06-14 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 17:07 [PATCH] target/s390x: Add a CONFIG switch to disable legacy CPUs Thomas Huth
2024-06-13 17:17 ` Philippe Mathieu-Daudé
2024-06-13 17:22 ` Thomas Huth
2024-06-13 17:37 ` Philippe Mathieu-Daudé
2024-06-14 6:07 ` Christian Borntraeger
2024-06-14 7:15 ` Thomas Huth
2024-06-14 8:17 ` Christian Borntraeger
2024-06-14 8:24 ` Thomas Huth [this message]
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=c752752a-c45c-4428-948f-b27c18510007@redhat.com \
--to=thuth@redhat.com \
--cc=anisinha@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).