From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: npiggin@gmail.com, "Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] ppc/spapr: fix default cpu for pre-10.0 machines.
Date: Thu, 13 Mar 2025 10:15:02 +0530 [thread overview]
Message-ID: <0eefc09a-138d-4b9d-90d8-c1796f4fed52@linux.ibm.com> (raw)
In-Reply-To: <89d61c6e-5a4e-49fc-a285-2215fa476709@linux.ibm.com>
On 3/12/25 15:50, Harsh Prateek Bora wrote:
>
>
> On 3/12/25 15:39, Philippe Mathieu-Daudé wrote:
>> On 12/3/25 06:58, Harsh Prateek Bora wrote:
>>> When POWER10 CPU was made as default, we missed keeping POWER9 as
>>> default for older pseries releases (pre-10.0) at that time.
>>> This caused breakge in default cpu evaluation for older pseries
>>> machines and hence this fix.
>>>
>>
>> Should we also include:
>>
>> Cc: qemu-stable@nongnu.org
>>
>> ?
>>
>
> I guess so. Not sure if we need a patch v2 for just that.
>
>>> Fixes: 51113013f3 ("ppc/spapr: change pseries machine default to
>>> POWER10 CPU")
>>> Signed-off-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
>>> ---
>>> hw/ppc/spapr.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>>> index c15340a58d..b31a91e2e2 100644
>>> --- a/hw/ppc/spapr.c
>>> +++ b/hw/ppc/spapr.c
>>> @@ -4748,6 +4748,7 @@ static void
>>> spapr_machine_9_2_class_options(MachineClass *mc)
>>> {
>>> spapr_machine_10_0_class_options(mc);
>>> compat_props_add(mc->compat_props, hw_compat_9_2,
>>> hw_compat_9_2_len);
>>> + mc->default_cpu_type = POWERPC_CPU_TYPE_NAME("power9_v2.2");
>>
>> This is confusing because v9.2 has already been released with that...
>
> I think it still needs to be fixed for v9.2 (and older) if someone wants
> to use pseries-9.2 (and older) with future releases.
Gave it another thought. May be moving the default to v9.1 could be
relatively better. 9.2 stable shall get the fix for pre-9.2 but 9.2
default need not change.
Nick, Daniel, comments?
Thanks
Harsh
>
> Thanks
> Harsh
>
>>
>>> }
>>> DEFINE_SPAPR_MACHINE(9, 2);
>>
>>
>
next prev parent reply other threads:[~2025-03-13 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 5:58 [PATCH] ppc/spapr: fix default cpu for pre-10.0 machines Harsh Prateek Bora
2025-03-12 10:09 ` Philippe Mathieu-Daudé
2025-03-12 10:20 ` Harsh Prateek Bora
2025-03-13 4:45 ` Harsh Prateek Bora [this message]
2025-03-13 9:32 ` Daniel P. Berrangé
2025-03-13 9:49 ` Harsh Prateek Bora
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=0eefc09a-138d-4b9d-90d8-c1796f4fed52@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).