From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Fabiano Rosas <farosas@linux.ibm.com>
Subject: Re: [PATCH v2 2/3] spapr: Add SPAPR_CAP_AIL_MODE_3 for AIL mode 3 support for H_SET_MODE hcall
Date: Mon, 28 Feb 2022 15:09:18 +0100 [thread overview]
Message-ID: <a5c7be8b-0f55-a671-651f-b8072ad1fbce@kaod.org> (raw)
In-Reply-To: <Yhwuwp+eAkiu6fnY@yekko>
>>>> + /* These tests match the CPU_FTR_P9_RADIX_PREFETCH_BUG flag in Linux */
>>>> + if (((pcc->pvr & 0xffffff00) == CPU_POWERPC_POWER9_DD1) ||
>>>> + ((pcc->pvr & 0xffffff00) == CPU_POWERPC_POWER9_DD20) ||
>>>> + ((pcc->pvr & 0xffffff00) == CPU_POWERPC_POWER9_DD21)) {
>>>> + return 0;
>>>> + }
>>>
>>> Deducing what KVM supports rather than getting it to tell us
>>> explicitly with a cap is usually frowned upon. However, given the
>>> earlier discussion, I'm satisfied that this is the least bad available
>>> option, at least for now.
>>
>> BTW this particular test doesn't work as I hoped because we only have
>> a power9 dd2.0 model.
>
> Oh.. yes... IIRC dd2.0 is barely present in the wild, since it doesn't
> have vital Spectre mitigations....
>
>> Adding a 2.2 or 2.3 would be possible. Maybe overkill. I'll change
>> the test just to catch all POWER9 for now.
>
> ... no, given the above, I think we should definitely add the newer
> models. Maybe even remove dd2.0 and replace it with the newer ones.
yes. It's really not a big effort.
Thanks,
C.
next prev parent reply other threads:[~2022-02-28 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 6:39 [PATCH v2 1/3] target/ppc: Fix POWER9 DD2.0 PVR, add DD2.1 Nicholas Piggin
2022-02-16 6:39 ` [PATCH v2 2/3] spapr: Add SPAPR_CAP_AIL_MODE_3 for AIL mode 3 support for H_SET_MODE hcall Nicholas Piggin
2022-02-17 0:17 ` David Gibson
2022-02-23 7:42 ` Nicholas Piggin
2022-02-28 2:09 ` David Gibson
2022-02-28 14:09 ` Cédric Le Goater [this message]
2022-02-16 6:39 ` [PATCH v2 3/3] target/ppc/kvm: Use KVM_CAP_PPC_AIL_MODE_3 to determine cap-ail-mode-3 support Nicholas Piggin
2022-02-17 0:19 ` David Gibson
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=a5c7be8b-0f55-a671-651f-b8072ad1fbce@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=farosas@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).