qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	Chinmay Rath <rathc@linux.ibm.com>, <qemu-ppc@nongnu.org>
Cc: <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH] target/ppc: Remove the unusable e200 CPUs
Date: Sat, 18 Oct 2025 08:01:02 +0200	[thread overview]
Message-ID: <3c2d1838-0fc9-46e3-a6b4-382ecc4d4ff8@kaod.org> (raw)
In-Reply-To: <295be472-7778-49f7-9ede-e5ef51dd908e@linux.ibm.com>

On 10/17/25 17:50, Harsh Prateek Bora wrote:
> 
> 
> On 10/17/25 20:15, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> There is currently no machine in QEMU (except the "none" machine)
>> that can be run with one of the e200 ppc CPUs - all machines either
>> complain about an invalid CPU type or crash QEMU immediatly.
>>
>> Looking at the history of this CPU type, it seems like it has never
>> been used in QEMU and only implemented as a placeholder (see e.g. the
>> comment about unimplemented instructions in the POWERPC_FAMILY(e200)
>> section of cpu_init.c). Being completely unused and unusable since
>> such a long time, let's just remove it now.
>>
>> Note: The init_excp_e200() is used by the e500 CPUs, too, so we
>> rename this function to init_excp_e500() instead of removing it.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   target/ppc/cpu-models.h |   4 --
>>   target/ppc/cpu-models.c |   5 --
>>   target/ppc/cpu_init.c   | 147 +---------------------------------------
>>   3 files changed, 2 insertions(+), 154 deletions(-)
>>
>> diff --git a/target/ppc/cpu-models.h b/target/ppc/cpu-models.h
>> index c6cd27f390e..a439eb37ee4 100644
>> --- a/target/ppc/cpu-models.h
>> +++ b/target/ppc/cpu-models.h
>> @@ -120,10 +120,6 @@ enum {
>>   #define CPU_POWERPC_MPC5200_v12      CPU_POWERPC_G2LEgp1
>>   #define CPU_POWERPC_MPC5200B_v20     CPU_POWERPC_G2LEgp1
>>   #define CPU_POWERPC_MPC5200B_v21     CPU_POWERPC_G2LEgp1
>> -    /* e200 family */
>> -    /* e200 cores */
>> -    CPU_POWERPC_e200z5             = 0x81000000,
>> -    CPU_POWERPC_e200z6             = 0x81120000,
>>       /* e300 family */
>>       /* e300 cores */
>>       CPU_POWERPC_e300c1             = 0x00830010,
>> diff --git a/target/ppc/cpu-models.c b/target/ppc/cpu-models.c
>> index 89ae763c7f6..26b6debcfc9 100644
>> --- a/target/ppc/cpu-models.c
>> +++ b/target/ppc/cpu-models.c
>> @@ -244,11 +244,6 @@
>>                       CPU_POWERPC_MPC5200B_v20, POWERPC_SVR_5200B_v20, G2LE)
>>       POWERPC_DEF_SVR("mpc5200b_v21", "MPC5200B v2.1",
>>                       CPU_POWERPC_MPC5200B_v21, POWERPC_SVR_5200B_v21, G2LE)
>> -    /* e200 family                                                           */
>> -    POWERPC_DEF("e200z5",        CPU_POWERPC_e200z5,                 e200,
>> -                "PowerPC e200z5 core")
>> -    POWERPC_DEF("e200z6",        CPU_POWERPC_e200z6,                 e200,
>> -                "PowerPC e200z6 core")
> 
> While I hope removal of e200 should be fine, I am thinking if we want to
> deprecate it in this cycle and remove it in next ?

Since it was never usable (I don't remember of any tests for these
CPUs), I agree with Thomas to bypass the deprecation process.



Thanks,

C.



  reply	other threads:[~2025-10-18  6:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 14:45 [RFC PATCH] target/ppc: Remove the unusable e200 CPUs Thomas Huth
2025-10-17 15:50 ` Harsh Prateek Bora
2025-10-18  6:01   ` Cédric Le Goater [this message]
2025-10-18  6:07     ` Harsh Prateek Bora
2025-10-20  4:24       ` Thomas Huth
2025-10-23 10:07 ` Harsh Prateek Bora
2025-10-23 14:48   ` Thomas Huth

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=3c2d1838-0fc9-46e3-a6b4-382ecc4d4ff8@kaod.org \
    --to=clg@kaod.org \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rathc@linux.ibm.com \
    --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).