From: Aditya Gupta <adityag@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Mahesh J Salgaonkar" <mahesh@linux.ibm.com>,
"Madhavan Srinivasan" <maddy@linux.ibm.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v5 0/8] Power11 support for QEMU [PowerNV]
Date: Tue, 25 Mar 2025 16:58:36 +0530 [thread overview]
Message-ID: <65c04078-e952-4806-bc3f-1f1130dc9683@linux.ibm.com> (raw)
In-Reply-To: <57ce8d50-db92-44f0-96a9-e1297eea949f@kaod.org>
Hi Cedric,
On 24/03/25 13:11, Cédric Le Goater wrote:
> Hello Aditya,
>
> On 3/8/25 21:51, Aditya Gupta wrote:
>> Overview
>> ============
>>
>> Add support for Power11 powernv machine type, to emulate PowerNV VMs
>> running on Power11.
>
> Could you please consider deprecating the POWER8NVL and POWER8E CPUs
> and associated chips and machines ? I think keeping POWER8 is fine
> since it has different HW implementation from the following generations.
> However, the POWER8NVL and POWER8E variants don't add much to QEMU.
> They were practical at one point for bringup (2014). They are not
> anymore.
>
> This will remove some lpc peculiarities.
I don't know how we 'mark' something deprecated in qemu. Checked the git
history.
By deprecating, should I just mention it in deprecated section in
documentation like done for PSeries in commit 0cac0f1b ?
Or directly remove it ?
Thanks,
- Aditya G
>
>
> Thanks,
>
> C.
>
next prev parent reply other threads:[~2025-03-25 11:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 20:51 [PATCH v5 0/8] Power11 support for QEMU [PowerNV] Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 1/8] ppc/pnv: Add HOMER for POWER11 Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 2/8] ppc/pnv: Add a LPC controller " Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 3/8] ppc/pnv: Add OCC for Power11 Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 4/8] ppc/pnv: Add a PSI bridge model " Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 5/8] ppc/pnv: Add SBE " Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 6/8] ppc/pnv: Add ChipTOD " Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 7/8] ppc/pnv: Add a Power11 Pnv11Chip, and a Power11 Machine Aditya Gupta
2025-03-09 14:08 ` Cédric Le Goater
2025-03-10 10:29 ` Aditya Gupta
2025-03-24 7:13 ` Aditya Gupta
2025-03-24 7:35 ` Cédric Le Goater
2025-03-24 8:38 ` Aditya Gupta
2025-03-08 20:51 ` [PATCH v5 8/8] ppc/pnv: Update skiboot to support Power11 Aditya Gupta
2025-03-09 14:10 ` Cédric Le Goater
2025-03-10 10:31 ` Aditya Gupta
2025-03-10 11:45 ` Cédric Le Goater
2025-03-10 14:59 ` Aditya Gupta
2025-03-10 15:33 ` Cédric Le Goater
2025-03-11 8:39 ` Nicholas Piggin
2025-03-11 8:46 ` Cédric Le Goater
2025-03-11 8:50 ` Aditya Gupta
2025-03-24 7:41 ` [PATCH v5 0/8] Power11 support for QEMU [PowerNV] Cédric Le Goater
2025-03-25 11:28 ` Aditya Gupta [this message]
2025-03-25 12:07 ` Cédric Le Goater
2025-03-25 17:11 ` Aditya Gupta
2025-03-25 17:16 ` Cédric Le Goater
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=65c04078-e952-4806-bc3f-1f1130dc9683@linux.ibm.com \
--to=adityag@linux.ibm.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=npiggin@gmail.com \
--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).