From: David Gibson <david@gibson.dropbear.id.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/ppc/spapr: Update H_GET_CPU_CHARACTERISTICS L1D cache flush bits
Date: Sat, 19 Jun 2021 19:26:39 +1000 [thread overview]
Message-ID: <YM24TwDm3SlCDiVu@yekko> (raw)
In-Reply-To: <20210615044107.1481608-1-npiggin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]
On Tue, Jun 15, 2021 at 02:41:07PM +1000, Nicholas Piggin wrote:
> There are several new L1D cache flush bits added to the hcall which reflect
> hardware security features for speculative cache access issues.
>
> These behaviours are now being specified as negative in order to simplify
> patched kernel compatibility with older firmware (a new problem found in
> existing systems would automatically be vulnerable).
I don't really understand all the consequences of that. What I need
to know here, is if it's safe to unconditionally enable these bits,
even for older machine types.
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> hw/ppc/spapr_hcall.c | 2 ++
> include/hw/ppc/spapr.h | 3 +++
> 2 files changed, 5 insertions(+)
>
> diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> index f25014afda..dfd9df469d 100644
> --- a/hw/ppc/spapr_hcall.c
> +++ b/hw/ppc/spapr_hcall.c
> @@ -1299,6 +1299,8 @@ static target_ulong h_get_cpu_characteristics(PowerPCCPU *cpu,
> behaviour |= H_CPU_BEHAV_L1D_FLUSH_PR;
> break;
> case SPAPR_CAP_FIXED:
> + behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY;
> + behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS;
> break;
> default: /* broken */
> assert(safe_cache == SPAPR_CAP_BROKEN);
> diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> index f05219f75e..0f25d081a8 100644
> --- a/include/hw/ppc/spapr.h
> +++ b/include/hw/ppc/spapr.h
> @@ -398,10 +398,13 @@ struct SpaprMachineState {
> #define H_CPU_CHAR_THR_RECONF_TRIG PPC_BIT(6)
> #define H_CPU_CHAR_CACHE_COUNT_DIS PPC_BIT(7)
> #define H_CPU_CHAR_BCCTR_FLUSH_ASSIST PPC_BIT(9)
> +
> #define H_CPU_BEHAV_FAVOUR_SECURITY PPC_BIT(0)
> #define H_CPU_BEHAV_L1D_FLUSH_PR PPC_BIT(1)
> #define H_CPU_BEHAV_BNDS_CHK_SPEC_BAR PPC_BIT(2)
> #define H_CPU_BEHAV_FLUSH_COUNT_CACHE PPC_BIT(5)
> +#define H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY PPC_BIT(7)
> +#define H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS PPC_BIT(8)
>
> /* Each control block has to be on a 4K boundary */
> #define H_CB_ALIGNMENT 4096
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-19 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 4:41 [PATCH] target/ppc/spapr: Update H_GET_CPU_CHARACTERISTICS L1D cache flush bits Nicholas Piggin
2021-06-19 9:26 ` David Gibson [this message]
2021-06-20 2:22 ` Nicholas Piggin
2021-07-05 5:12 ` David Gibson
2021-07-08 3:54 ` 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=YM24TwDm3SlCDiVu@yekko \
--to=david@gibson.dropbear.id.au \
--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 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.