From: "Cédric Le Goater" <clg@redhat.com>
To: "Aditya Gupta" <adityag@linux.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: Harsh Prateek Bora <harshpb@linux.ibm.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v7 0/2] Deprecate Power8E and Power8NVL
Date: Fri, 8 Aug 2025 09:15:56 +0200 [thread overview]
Message-ID: <5b9e0a81-c2d9-4c55-b761-a43a69ec400c@redhat.com> (raw)
In-Reply-To: <20250607110412.2342511-1-adityag@linux.ibm.com>
On 6/7/25 13:04, Aditya Gupta wrote:
> Note: No changes, only change compared to v6 is rebased to upstream
>
> Power8E and Power8NVL are not maintained, and not useful to qemu, and
> upstream skiboot also has removed support till Power8 DD1.
> Power8NVL CPU doesn't boot since skiboot v7.0, or following skiboot commit
> to be exact:
>
> commit c5424f683ee3 ("Remove support for POWER8 DD1")
>
> No direct way to deprecate the pnv chips, a field like deprecation_note
> could be added, but felt not needed as the chip will only get used if
> the user requests corresponding 8E / 8NVL CPU, which will print
> deprecation warning.
>
> Also, no separate pnv machine for 8E and 8NVL, user has to pass --cpu,
> which will throw the deprecation warning. So just deprecating CPUs should
> be enough.
>
> Changelog
> =========
> v7:
> + rebased to upstream
> v6:
> + change qemu version from 10.0 to 10.1 in doc
> v5 (https://lore.kernel.org/qemu-devel/20250422043843.26115-1-adityag@linux.ibm.com/):
> + split into 2 patches, defining macro, and deprecating 8e & 8nvl
> v4 (https://lore.kernel.org/qemu-devel/20250330211012.2932258-1-adityag@linux.ibm.com/):
> + remove unnecessary 'if'
> v3:
> + add 'deprecation_note' argument to the POWERPC_DEPRECATED_CPU macro
> v2:
> + add mention to docs/about/deprecated.rst
> + add '(deprecated)' in output of qemu-system-ppc64 --cpu help
>
> Base Commit: 96215036f47403438c7c7869b7cd419bd7a11f82
>
> Aditya Gupta (2):
> target/ppc: Introduce macro for deprecating PowerPC CPUs
> target/ppc: Deprecate Power8E and Power8NVL
>
> docs/about/deprecated.rst | 9 +++++++++
> target/ppc/cpu-models.c | 20 +++++++++++++++-----
> target/ppc/cpu_init.c | 7 ++++++-
> 3 files changed, 30 insertions(+), 6 deletions(-)
>
It's too late for QEMU 10.1. Let's not forget these for the next cycle.
Thanks,
C.
next prev parent reply other threads:[~2025-08-08 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 11:04 [PATCH v7 0/2] Deprecate Power8E and Power8NVL Aditya Gupta
2025-06-07 11:04 ` [PATCH v7 1/2] target/ppc: Introduce macro for deprecating PowerPC CPUs Aditya Gupta
2025-06-07 11:04 ` [PATCH v7 2/2] target/ppc: Deprecate Power8E and Power8NVL Aditya Gupta
2025-06-23 8:23 ` [PATCH v7 0/2] " Aditya Gupta
2025-08-08 7:15 ` Cédric Le Goater [this message]
2025-08-08 7:19 ` Harsh Prateek Bora
2025-09-23 7:40 ` Anushree Mathur
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=5b9e0a81-c2d9-4c55-b761-a43a69ec400c@redhat.com \
--to=clg@redhat.com \
--cc=adityag@linux.ibm.com \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.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).