All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Chanho Park <parkch98@gmail.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: add Cortex-A76 to spectre v2 safe-list
Date: Mon, 13 Jan 2020 09:22:05 +0000	[thread overview]
Message-ID: <81a4e97c116e5cb4378092411069a80e@kernel.org> (raw)
In-Reply-To: <20200112151014.2593-1-parkch98@gmail.com>

On 2020-01-12 15:10, Chanho Park wrote:
> Cortex A76(Enyo) core can be added in spectre v2(CVE-2017-5715 
> (Spectre,
> Variant 2, Branch Target Injection) safe list.
> 
> Signed-off-by: Chanho Park <parkch98@gmail.com>
> ---
>  arch/arm64/kernel/cpu_errata.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/kernel/cpu_errata.c 
> b/arch/arm64/kernel/cpu_errata.c
> index 85f4bec22f6d..9895d56bf5ac 100644
> --- a/arch/arm64/kernel/cpu_errata.c
> +++ b/arch/arm64/kernel/cpu_errata.c
> @@ -546,6 +546,7 @@ static const struct midr_range 
> spectre_v2_safe_list[] = {
>  	MIDR_ALL_VERSIONS(MIDR_CORTEX_A35),
>  	MIDR_ALL_VERSIONS(MIDR_CORTEX_A53),
>  	MIDR_ALL_VERSIONS(MIDR_CORTEX_A55),
> +	MIDR_ALL_VERSIONS(MIDR_CORTEX_A76),
>  	MIDR_ALL_VERSIONS(MIDR_BRAHMA_B53),
>  	MIDR_ALL_VERSIONS(MIDR_HISI_TSV110),
>  	{ /* sentinel */ }

Why? Doesn't Cortex-A76 already advertize ID_AA64PFR0_EL1.CSV2?

         M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-01-13  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 15:10 [PATCH] arm64: add Cortex-A76 to spectre v2 safe-list Chanho Park
2020-01-13  9:22 ` Marc Zyngier [this message]

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=81a4e97c116e5cb4378092411069a80e@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=parkch98@gmail.com \
    --cc=will@kernel.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.