qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>, 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:57:34 +1000	[thread overview]
Message-ID: <CSNM2WXID5Q1.31EUVHXGPD66F@wheely> (raw)
In-Reply-To: <5b7f36b4-99f5-cba5-9c16-fc03457137b5@kaod.org>

On Tue May 16, 2023 at 6:44 PM AEST, Cédric Le Goater wrote:
> On 5/15/23 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.
>
> I would remove power9_v1.0 and power9_v2.0 (not shipped AFAIK) and maybe
> add power9_v2.3 since it has a little more features.

Yes to removing DD1 (and for P10), and adding 2.3. Not sure about
removing 2.0, we carry this radix MMU prefetch workaround thing for
2.0 and 2.1 in upstream KVM which causes some of this AIL-3
complication.

Having a 2.0 model might help with that, and if it doesn't cause
much effort to maintain I'd like to keep it for a bit. Can remove
it if upstream KVM drops support or it causes problems.

Thanks,
Nick


  reply	other threads:[~2023-05-16  9:58 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
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 [this message]
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=CSNM2WXID5Q1.31EUVHXGPD66F@wheely \
    --to=npiggin@gmail.com \
    --cc=clg@kaod.org \
    --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 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).