qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Murilo Opsfelder Araújo" <muriloo@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"David Gibson" <david@gibson.dropbear.id.au>,
	"Greg Kurz" <groug@kaod.org>,
	mopsfelder@gmail.com, "Daniel P . Berrangé" <berrange@redhat.com>,
	"Fabiano Rosas" <farosas@linux.ibm.com>
Subject: Re: [PATCH] target/ppc/cpu-models: Update max alias to power10
Date: Thu, 2 Jun 2022 09:01:21 -0300	[thread overview]
Message-ID: <39dbde9e-1287-c6f2-32aa-c2a575791ef1@linux.ibm.com> (raw)
In-Reply-To: <5435bc6f-70c4-4a18-72b7-147ada5f6a1b@kaod.org>

Hi, Cédric.

On 6/1/22 04:44, Cédric Le Goater wrote:
> On 6/1/22 09:27, Thomas Huth wrote:
>> On 31/05/2022 19.27, Murilo Opsfelder Araujo wrote:
>>> Update max alias to power10 so users can take advantage of a more
>>> recent CPU model when '-cpu max' is provided.
>>>
>>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1038
>>> Cc: Daniel P. Berrangé <berrange@redhat.com>
>>> Cc: Thomas Huth <thuth@redhat.com>
>>> Cc: Cédric Le Goater <clg@kaod.org>
>>> Cc: Daniel Henrique Barboza <danielhb413@gmail.com>
>>> Cc: Fabiano Rosas <farosas@linux.ibm.com>
>>> Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
>>> ---
>>>   target/ppc/cpu-models.c | 3 ++-
>>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/target/ppc/cpu-models.c b/target/ppc/cpu-models.c
>>> index 976be5e0d1..c15fcb43a1 100644
>>> --- a/target/ppc/cpu-models.c
>>> +++ b/target/ppc/cpu-models.c
>>> @@ -879,7 +879,6 @@ PowerPCCPUAlias ppc_cpu_aliases[] = {
>>>       { "755", "755_v2.8" },
>>>       { "goldfinger", "755_v2.8" },
>>>       { "7400", "7400_v2.9" },
>>> -    { "max", "7400_v2.9" },
>>>       { "g4",  "7400_v2.9" },
>>>       { "7410", "7410_v1.4" },
>>>       { "nitro", "7410_v1.4" },
>>> @@ -910,6 +909,8 @@ PowerPCCPUAlias ppc_cpu_aliases[] = {
>>>       { "power8nvl", "power8nvl_v1.0" },
>>>       { "power9", "power9_v2.0" },
>>>       { "power10", "power10_v2.0" },
>>> +    /* Update the 'max' alias to the latest CPU model */
>>> +    { "max", "power10_v2.0" },
>>>   #endif
>>
>> I'm not sure whether "max" should really be fixed alias in this list here? What if a user runs with KVM on a POWER8 host - then "max" won't work this way, will it?
>>
>> And in the long run, it would also be good if this would work with other machines like the "g3beige", too (which don't support the new 64-bit POWER CPUs), so you should at least mention in the commit description that this is only a temporary hack for the pseries machine, I think.
>
> Yes. You are right, Thomas.
>
> s390 and x86 have a nice way to address "max".

If I understood the code correctly, they implement "-cpu max" based on
a CPU model with additional CPU features enabled.  The resulting
emulated CPU is not necessarily a CPU model that exists as a hardware.
So, the "-cpu max" never gets any CPU feature dropped.  Features are
only added in.

I'm not keen on this idea of having a CPU model that doesn't even
exist as a hardware.

--
Murilo



  reply	other threads:[~2022-06-02 12:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 17:27 [PATCH] target/ppc/cpu-models: Update max alias to power10 Murilo Opsfelder Araujo
2022-05-31 17:52 ` Cédric Le Goater
2022-05-31 18:04 ` Matheus K. Ferst
2022-06-02 12:23   ` Murilo Opsfelder Araújo
2022-06-01  7:27 ` Thomas Huth
2022-06-01  7:44   ` Cédric Le Goater
2022-06-02 12:01     ` Murilo Opsfelder Araújo [this message]
2022-06-01  8:38   ` Greg Kurz
2022-06-01  9:25     ` Thomas Huth
2022-06-01  9:59       ` Daniel Henrique Barboza
2022-06-02 12:18         ` Murilo Opsfelder Araújo
2022-06-01 10:03       ` Greg Kurz
2022-06-01 10:35         ` Daniel Henrique Barboza
2022-06-06 10:59         ` Daniel P. Berrangé
2022-06-02 12:10     ` Murilo Opsfelder Araújo
2022-06-02 13:23       ` Greg Kurz
2022-06-02 11:49   ` Murilo Opsfelder Araújo

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=39dbde9e-1287-c6f2-32aa-c2a575791ef1@linux.ibm.com \
    --to=muriloo@linux.ibm.com \
    --cc=berrange@redhat.com \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=farosas@linux.ibm.com \
    --cc=groug@kaod.org \
    --cc=mopsfelder@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 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).