public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Trilok Soni <quic_tsoni@quicinc.com>
To: Douglas Anderson <dianders@chromium.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Roxana Bradescu <roxabee@google.com>,
	Julius Werner <jwerner@chromium.org>,
	<bjorn.andersson@oss.qualcomm.com>,
	<linux-arm-msm@vger.kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	<linux-arm-kernel@lists.infradead.org>,
	Jeffrey Hugo <quic_jhugo@quicinc.com>,
	Scott Bauer <sbauer@quicinc.com>, <stable@vger.kernel.org>,
	James Morse <james.morse@arm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/5] arm64: errata: Add KRYO 2XX/3XX/4XX silver cores to Spectre BHB safe list
Date: Fri, 7 Feb 2025 14:57:30 -0800	[thread overview]
Message-ID: <04adfe6c-5f04-4e28-a52d-b8cb5654771a@quicinc.com> (raw)
In-Reply-To: <20250107120555.v4.3.Iab8dbfb5c9b1e143e7a29f410bce5f9525a0ba32@changeid>

On 1/7/2025 12:06 PM, Douglas Anderson wrote:
> Qualcomm has confirmed that, much like Cortex A53 and A55, KRYO
> 2XX/3XX/4XX silver cores are unaffected by Spectre BHB. Add them to
> the safe list.
> 
> 
> Fixes: 558c303c9734 ("arm64: Mitigate spectre style branch history side channels")
> Cc: stable@vger.kernel.org
> Cc: Scott Bauer <sbauer@quicinc.com>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
> 
> Changes in v4:
> - Re-added KRYO 2XX/3XX/4XX silver patch after Qualcomm confirmed.
> 
> Changes in v3:
> - Removed KRYO 2XX/3XX/4XX silver patch.
> 
> Changes in v2:
> - New
> 
>  arch/arm64/kernel/proton-pack.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/arch/arm64/kernel/proton-pack.c b/arch/arm64/kernel/proton-pack.c
> index 17aa836fe46d..89405be53d8f 100644
> --- a/arch/arm64/kernel/proton-pack.c
> +++ b/arch/arm64/kernel/proton-pack.c
> @@ -854,6 +854,9 @@ static bool is_spectre_bhb_safe(int scope)
>  		MIDR_ALL_VERSIONS(MIDR_CORTEX_A510),
>  		MIDR_ALL_VERSIONS(MIDR_CORTEX_A520),
>  		MIDR_ALL_VERSIONS(MIDR_BRAHMA_B53),
> +		MIDR_ALL_VERSIONS(MIDR_QCOM_KRYO_2XX_SILVER),
> +		MIDR_ALL_VERSIONS(MIDR_QCOM_KRYO_3XX_SILVER),
> +		MIDR_ALL_VERSIONS(MIDR_QCOM_KRYO_4XX_SILVER),
>  		{},
>  	};
>  	static bool all_safe = true;

Acked-by: Trilok Soni <quic_tsoni@quicinc.com>

-- 
---Trilok Soni


  reply	other threads:[~2025-02-07 23:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 20:05 [PATCH v4 0/5] arm64: errata: Rework Spectre BHB mitigations to not assume "safe" Douglas Anderson
2025-01-07 20:05 ` [PATCH v4 1/5] arm64: errata: Add QCOM_KRYO_4XX_GOLD to the spectre_bhb_k24_list Douglas Anderson
2025-02-07 22:56   ` Trilok Soni
2025-01-07 20:05 ` [PATCH v4 2/5] arm64: errata: Assume that unknown CPUs _are_ vulnerable to Spectre BHB Douglas Anderson
2025-01-29 16:43   ` James Morse
2025-01-29 19:14     ` Doug Anderson
2025-02-12 17:52       ` Catalin Marinas
2025-02-12 18:05         ` Doug Anderson
2025-01-07 20:06 ` [PATCH v4 3/5] arm64: errata: Add KRYO 2XX/3XX/4XX silver cores to Spectre BHB safe list Douglas Anderson
2025-02-07 22:57   ` Trilok Soni [this message]
2025-01-07 20:06 ` [PATCH v4 4/5] arm64: cputype: Add MIDR_CORTEX_A76AE Douglas Anderson
2025-01-07 20:06 ` [PATCH v4 5/5] arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists Douglas Anderson
2025-01-29 16:43   ` James Morse
2025-03-14 18:42 ` [PATCH v4 0/5] arm64: errata: Rework Spectre BHB mitigations to not assume "safe" Catalin Marinas

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=04adfe6c-5f04-4e28-a52d-b8cb5654771a@quicinc.com \
    --to=quic_tsoni@quicinc.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=catalin.marinas@arm.com \
    --cc=dianders@chromium.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=james.morse@arm.com \
    --cc=jwerner@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=quic_jhugo@quicinc.com \
    --cc=roxabee@google.com \
    --cc=sbauer@quicinc.com \
    --cc=stable@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox