From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
devel@lists.libvirt.org,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH-for-9.0] docs: Deprecate the pseries-2.12 machines
Date: Tue, 12 Mar 2024 15:02:14 +1000 [thread overview]
Message-ID: <CZRIARPDRC29.2377OJOQHTV2J@wheely> (raw)
In-Reply-To: <20240311190459.66334-1-philmd@linaro.org>
On Tue Mar 12, 2024 at 5:04 AM AEST, Philippe Mathieu-Daudé wrote:
> pSeries machines before 3.0 have complex migration back
> compatibility code we'd like to get ride of. The last
> one is 2.12, which is 6 years old. We just deprecated up
> to the 2.11 machine in commit 1392617d35 ("spapr: Tag
> pseries-2.1 - 2.11 machines as deprecated").
> Take to opportunity to also deprecate the 2.12 machines.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> In 2025 I'd like to get ride of the code related to:
>
> include/hw/ppc/spapr_cpu_core.h:31: bool pre_3_0_migration; /* older machine don't know about SpaprCpuState */
Acked-by: Nicholas Piggin <npiggin@gmail.com>
I can merge this via the PPC tree.
Thanks,
Nick
> ---
> docs/about/deprecated.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index dfd681cd02..65111513cc 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -237,13 +237,13 @@ The Nios II architecture is orphan.
> The machine is no longer in existence and has been long unmaintained
> in QEMU. This also holds for the TC51828 16MiB flash that it uses.
>
> -``pseries-2.1`` up to ``pseries-2.11`` (since 9.0)
> +``pseries-2.1`` up to ``pseries-2.12`` (since 9.0)
> ''''''''''''''''''''''''''''''''''''''''''''''''''
>
> -Older pseries machines before version 2.12 have undergone many changes
> +Older pseries machines before version 3.0 have undergone many changes
> to correct issues, mostly regarding migration compatibility. These are
> no longer maintained and removing them will make the code easier to
> -read and maintain. Use versions 2.12 and above as a replacement.
> +read and maintain. Use versions 3.0 and above as a replacement.
>
> Backend options
> ---------------
prev parent reply other threads:[~2024-03-12 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 19:04 [PATCH-for-9.0] docs: Deprecate the pseries-2.12 machines Philippe Mathieu-Daudé
2024-03-12 5:02 ` Nicholas Piggin [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=CZRIARPDRC29.2377OJOQHTV2J@wheely \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=devel@lists.libvirt.org \
--cc=harshpb@linux.ibm.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).