From: D Scott Phillips <scott@os.amperecomputing.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
Oliver Upton <oliver.upton@linux.dev>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
Besar Wicaksono <bwicaksono@nvidia.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Rob Herring <robh@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org, patches@amperecomputing.com,
Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH] arm64: errata: Enable the AC03_CPU_38 workaround for ampere1a
Date: Tue, 27 Aug 2024 09:02:58 -0700 [thread overview]
Message-ID: <86zfoy2bt9.fsf@scott-ph-mail.amperecomputing.com> (raw)
In-Reply-To: <314b8893-2ffd-4148-974b-725cfaa97d18@arm.com>
Anshuman Khandual <anshuman.khandual@arm.com> writes:
> On 8/27/24 04:53, Oliver Upton wrote:
>> Hi D Scott,
>>
>> On Mon, Aug 26, 2024 at 02:59:33PM -0700, D Scott Phillips wrote:
>>> The ampere1a cpu is affected by erratum AC04_CPU_10 which is the same
>>> bug as AC03_CPU38. Add ampere1a to the AC03_CPU_38 workaround midr list.
>>>
>>> Signed-off-by: D Scott Phillips <scott@os.amperecomputing.com>
>>> ---
>>> Documentation/arch/arm64/silicon-errata.rst | 2 ++
>>> arch/arm64/Kconfig | 2 +-
>>> arch/arm64/include/asm/cputype.h | 2 ++
>>> arch/arm64/kernel/cpu_errata.c | 1 +
>>> 4 files changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/arch/arm64/silicon-errata.rst b/Documentation/arch/arm64/silicon-errata.rst
>>> index 50327c05be8d1..39c52385f11fb 100644
>>> --- a/Documentation/arch/arm64/silicon-errata.rst
>>> +++ b/Documentation/arch/arm64/silicon-errata.rst
>>> @@ -55,6 +55,8 @@ stable kernels.
>>> +----------------+-----------------+-----------------+-----------------------------+
>>> | Ampere | AmpereOne | AC03_CPU_38 | AMPERE_ERRATUM_AC03_CPU_38 |
>>> +----------------+-----------------+-----------------+-----------------------------+
>>> +| Ampere | AmpereOne AC04 | AC04_CPU_10 | AMPERE_ERRATUM_AC03_CPU_38 |
>>> ++----------------+-----------------+-----------------+-----------------------------+
>>
>> We tend to stick the marketing term for a part in the second column so
>> it is more recognizable for the user. Is this a placeholder for something
>> different from "ampere1a"?
>
> Agreed, even the MIDR being added here is for AMPERE1A. Probably something
> like 'AmpereOneA' might be more suitable.
"AmpereOne AC04" was given to me by our marketing department, so that
should be the user visible name of the part when they buy/use
it. ampere1a is the name of the core in the SoC and the thing you can
use in gcc's --mtune=, similar to "neoverse-n1" within "Ampere Altra".
>>
>>> diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
>>> index f6b6b45073571..748aa536446ae 100644
>>> --- a/arch/arm64/kernel/cpu_errata.c
>>> +++ b/arch/arm64/kernel/cpu_errata.c
>>> @@ -773,6 +773,7 @@ const struct arm64_cpu_capabilities arm64_errata[] = {
>>> .desc = "AmpereOne erratum AC03_CPU_38",
>>> .capability = ARM64_WORKAROUND_AMPERE_AC03_CPU_38,
>>> ERRATA_MIDR_ALL_VERSIONS(MIDR_AMPERE1),
>>> + ERRATA_MIDR_ALL_VERSIONS(MIDR_AMPERE1A),
>>
>> This will break the workaround on AC03, since the second macro reassigns
>> ::midr_range.
>>
>> You'll want to use ERRATA_MIDR_RANGE_LIST() instead w/ an array of
>> affected MIDRs.
>>
>
> +1
>
> Although ERRATA_MIDR_RANGE_LIST() in turn creates such a list.
Oops, my mistake. I'll fix this.
prev parent reply other threads:[~2024-08-27 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 21:59 [PATCH] arm64: errata: Enable the AC03_CPU_38 workaround for ampere1a D Scott Phillips
2024-08-26 23:23 ` Oliver Upton
2024-08-26 23:28 ` Oliver Upton
2024-08-27 1:52 ` Anshuman Khandual
2024-08-27 16:02 ` D Scott Phillips [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=86zfoy2bt9.fsf@scott-ph-mail.amperecomputing.com \
--to=scott@os.amperecomputing.com \
--cc=andre.przywara@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=eahariha@linux.microsoft.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=patches@amperecomputing.com \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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).