From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Frederic Barrat" <fbarrat@linux.ibm.com>, <qemu-ppc@nongnu.org>
Cc: <qemu-devel@nongnu.org>, "Harsh Prateek Bora" <harsh@linux.vnet.ibm.com>
Subject: Re: [PATCH v4] target/ppc: Add POWER9 DD2.2 model
Date: Tue, 16 May 2023 19:44:13 +1000 [thread overview]
Message-ID: <CSNLSP464PKJ.3NNMBKX65EUWI@wheely> (raw)
In-Reply-To: <efda933a-7a14-7157-887d-28137c872895@linux.ibm.com>
On Tue May 16, 2023 at 5:56 PM AEST, Frederic Barrat wrote:
>
>
> On 15/05/2023 18:02, Nicholas Piggin wrote:
> > POWER9 DD2.1 and earlier had significant limitations when running KVM,
> > including lack of "mixed mode" MMU support (ability to run HPT and RPT
> > mode on threads of the same core), and a translation prefetch issue
> > which is worked around by disabling "AIL" mode for the guest.
> >
> > These processors are not widely available, and it's difficult to deal
> > with all these quirks in qemu +/- KVM, so create a POWER9 DD2.2 CPU
> > and make it the default POWER9 CPU.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
>
> Reviewed-by: Frederic Barrat <fbarrat@linux.ibm.com>
>
> Which makes me wonder if the P9 DD1 and P10 DD1 cpu definitions are
> worth keeping, since we don't really try emulating the differences and
> we don't support them in firmware/skiboot. The only place where we seem
> to bother is in target/ppc/kvm.c and that's precisely what this patch is
> trying to avoid.
+1. We could do a follow up as Cedric suggested.
Thanks,
Nick
next prev parent reply other threads:[~2023-05-16 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 16:02 [PATCH v4] target/ppc: Add POWER9 DD2.2 model Nicholas Piggin
2023-05-16 7:56 ` Frederic Barrat
2023-05-16 9:44 ` Nicholas Piggin [this message]
2023-05-16 7:58 ` Frederic Barrat
2023-05-16 9:41 ` Nicholas Piggin
2023-05-16 8:44 ` Cédric Le Goater
2023-05-16 9:57 ` Nicholas Piggin
2023-05-16 9:23 ` Harsh Prateek Bora
2023-05-16 10:14 ` Nicholas Piggin
2023-05-28 16:15 ` Daniel Henrique Barboza
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=CSNLSP464PKJ.3NNMBKX65EUWI@wheely \
--to=npiggin@gmail.com \
--cc=fbarrat@linux.ibm.com \
--cc=harsh@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.