All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Marc Zyngier <maz@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	martin.botka@somainline.org,
	angelogioacchino.delregno@somainline.org,
	marijn.suijten@somainline.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Stephen Boyd <swboyd@chromium.org>,
	Rob Herring <robh@kernel.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Steven Price <steven.price@arm.com>,
	Mark Brown <broonie@kernel.org>, Andrew Scull <ascull@google.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	Ionela Voinescu <ionela.voinescu@arm.com>,
	Kristina Martsenko <kristina.martsenko@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: cpu_errata: Apply Erratum 845719 to KRYO2XX Silver
Date: Mon, 09 Nov 2020 15:06:35 +0530	[thread overview]
Message-ID: <8771f66911522ab87fe1b9b16e4e9921@codeaurora.org> (raw)
In-Reply-To: <3faa81d537320dfb20bb3f882cfaea1b@kernel.org>

Hi Marc,

On 2020-11-05 14:59, Marc Zyngier wrote:
> On 2020-11-04 23:22, Konrad Dybcio wrote:
>> QCOM KRYO2XX Silver cores are Cortex-A53 based and are
>> susceptible to the 845719 erratum. Add them to the lookup
>> list to apply the erratum.
>> 
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
>> ---
>>  arch/arm64/kernel/cpu_errata.c | 2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/arch/arm64/kernel/cpu_errata.c 
>> b/arch/arm64/kernel/cpu_errata.c
>> index 61314fd70f13..cafaf0da05b7 100644
>> --- a/arch/arm64/kernel/cpu_errata.c
>> +++ b/arch/arm64/kernel/cpu_errata.c
>> @@ -299,6 +299,8 @@ static const struct midr_range 
>> erratum_845719_list[] = {
>>  	MIDR_REV_RANGE(MIDR_CORTEX_A53, 0, 0, 4),
>>  	/* Brahma-B53 r0p[0] */
>>  	MIDR_REV(MIDR_BRAHMA_B53, 0, 0),
>> +	/* Kryo2XX Silver rAp4 */
>> +	MIDR_REV(MIDR_QCOM_KRYO_2XX_SILVER, 0xa, 0x4),
> 
> Is this the only affected version? If this is actually an A53, how do 
> the
> revisions map between Kryo and Cortex cores?
> 

 From what I see from the docs, this is the only version used
in MSM8998(silver cores are based on Cortex A53) and it maps
to r0p4. @Konrad, can you include (rap4 => r0p4) in comment.

Thanks,
Sai

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

WARNING: multiple messages have this Message-ID (diff)
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Marc Zyngier <maz@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Rob Herring <robh@kernel.org>,
	Ionela Voinescu <ionela.voinescu@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-kernel@vger.kernel.org,
	Kristina Martsenko <kristina.martsenko@arm.com>,
	Stephen Boyd <swboyd@chromium.org>,
	Mark Brown <broonie@kernel.org>,
	martin.botka@somainline.org,
	~postmarketos/upstreaming@lists.sr.ht,
	angelogioacchino.delregno@somainline.org,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	marijn.suijten@somainline.org, phone-devel@vger.kernel.org,
	Will Deacon <will@kernel.org>,
	Steven Price <steven.price@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Andrew Scull <ascull@google.com>
Subject: Re: [PATCH 4/4] arm64: cpu_errata: Apply Erratum 845719 to KRYO2XX Silver
Date: Mon, 09 Nov 2020 15:06:35 +0530	[thread overview]
Message-ID: <8771f66911522ab87fe1b9b16e4e9921@codeaurora.org> (raw)
In-Reply-To: <3faa81d537320dfb20bb3f882cfaea1b@kernel.org>

Hi Marc,

On 2020-11-05 14:59, Marc Zyngier wrote:
> On 2020-11-04 23:22, Konrad Dybcio wrote:
>> QCOM KRYO2XX Silver cores are Cortex-A53 based and are
>> susceptible to the 845719 erratum. Add them to the lookup
>> list to apply the erratum.
>> 
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
>> ---
>>  arch/arm64/kernel/cpu_errata.c | 2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/arch/arm64/kernel/cpu_errata.c 
>> b/arch/arm64/kernel/cpu_errata.c
>> index 61314fd70f13..cafaf0da05b7 100644
>> --- a/arch/arm64/kernel/cpu_errata.c
>> +++ b/arch/arm64/kernel/cpu_errata.c
>> @@ -299,6 +299,8 @@ static const struct midr_range 
>> erratum_845719_list[] = {
>>  	MIDR_REV_RANGE(MIDR_CORTEX_A53, 0, 0, 4),
>>  	/* Brahma-B53 r0p[0] */
>>  	MIDR_REV(MIDR_BRAHMA_B53, 0, 0),
>> +	/* Kryo2XX Silver rAp4 */
>> +	MIDR_REV(MIDR_QCOM_KRYO_2XX_SILVER, 0xa, 0x4),
> 
> Is this the only affected version? If this is actually an A53, how do 
> the
> revisions map between Kryo and Cortex cores?
> 

 From what I see from the docs, this is the only version used
in MSM8998(silver cores are based on Cortex A53) and it maps
to r0p4. @Konrad, can you include (rap4 => r0p4) in comment.

Thanks,
Sai

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

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

  parent reply	other threads:[~2020-11-09  9:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 23:22 [PATCH 0/4] Add KRYO2XX Errata / mitigations data Konrad Dybcio
2020-11-04 23:22 ` Konrad Dybcio
2020-11-04 23:22 ` [PATCH 1/4] arm64: Add MIDR value for KRYO2XX gold/silver CPU cores Konrad Dybcio
2020-11-04 23:22   ` Konrad Dybcio
2020-11-04 23:22 ` [PATCH 2/4] arm64: kpti: Add KRYO2XX gold/silver CPU cores to kpti safelist Konrad Dybcio
2020-11-04 23:22   ` Konrad Dybcio
2020-11-04 23:22 ` [PATCH 3/4] arm64: proton-pack: Add KRYO2XX silver CPUs to spectre-v2 safe-list Konrad Dybcio
2020-11-04 23:22   ` Konrad Dybcio
2020-11-04 23:22 ` [PATCH 4/4] arm64: cpu_errata: Apply Erratum 845719 to KRYO2XX Silver Konrad Dybcio
2020-11-04 23:22   ` Konrad Dybcio
2020-11-05  9:29   ` Marc Zyngier
2020-11-05  9:29     ` Marc Zyngier
2020-11-05 11:24     ` Konrad Dybcio
2020-11-05 11:24       ` Konrad Dybcio
2020-11-09  9:36     ` Sai Prakash Ranjan [this message]
2020-11-09  9:36       ` Sai Prakash Ranjan
2020-11-09 19:28       ` Konrad Dybcio
2020-11-09 19:28         ` Konrad Dybcio
2020-11-10  5:56         ` Sai Prakash Ranjan
2020-11-10  5:56           ` Sai Prakash Ranjan
2020-11-05  9:33 ` [PATCH 0/4] Add KRYO2XX Errata / mitigations data Will Deacon
2020-11-05  9:33   ` Will Deacon
2020-11-10  7:00   ` Sai Prakash Ranjan
2020-11-10  7:00     ` Sai Prakash Ranjan
2020-11-13 11:27 ` Will Deacon
2020-11-13 11:27   ` Will Deacon

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=8771f66911522ab87fe1b9b16e4e9921@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=amit.kachhap@arm.com \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ascull@google.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=ionela.voinescu@arm.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=kristina.martsenko@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=maz@kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=steven.price@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=swboyd@chromium.org \
    --cc=will@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.