From: Nick Chan <towinchenmi@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: asahi@lists.linux.dev, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v2 2/2] arm64: cpufeature: Pretend that Apple A10 family does not support 32-bit EL0
Date: Mon, 16 Sep 2024 21:41:12 +0800 [thread overview]
Message-ID: <f908c9ca-8063-44f4-b534-ddfc067b98c2@gmail.com> (raw)
In-Reply-To: <20240909091425.16258-3-towinchenmi@gmail.com>
On 9/9/2024 17:10, Nick Chan wrote:
> The Apple A10 family consists of physical performance and efficiency
> cores, and only one of them can be active at a given time depending on
> the current p-state. However, only the performance cores can execute
> 32-bit EL0. This results in logical cores that can only execute 32-bit
> EL0 in high p-states.
Further research shows that the MPIDR_EL1 values between the two core
types are different. And whether the two core type have any extra
differences is anyone's guess right now. So far, nothing seems to break
horribly without special workarounds for the MPIDR value (with cpufreq
enabled downstream) as:
1. There are no KVM, GIC, ACPI, PSCI or cpuidle
2. All CPUs switch P-mode and E-mode together
However, all of this is broken enough that this piece of code should go
into arch/arm64/kernel/cpu_errata.c, and also generate a
TAINT_CPU_OUT_OF_SPEC for these cursed CPUs.
>
> Trying to support 32-bit EL0 on a CPU that can only execute it in certain
> states is a bad idea. The A10 family only supports 16KB page size anyway
> so many AArch32 executables won't run anyways. Pretend that it does not
> support 32-bit EL0 at all.
>
> Signed-off-by: Nick Chan <towinchenmi@gmail.com>
> ---
> arch/arm64/kernel/cpufeature.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index 718728a85430..386698f42172 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -3529,6 +3529,31 @@ void __init setup_boot_cpu_features(void)
> setup_boot_cpu_capabilities();
> }
>
> +static void __init bad_aarch32_el0_fixup(void)
> +{
> + static const struct midr_range bad_aarch32_el0[] = {
> + MIDR_ALL_VERSIONS(MIDR_APPLE_A10_T2_HURRICANE_ZEPHYR),
> + MIDR_ALL_VERSIONS(MIDR_APPLE_A10X_HURRICANE_ZEPHYR),
> + {}
> + };
> +
> + /*
> + * The Apple A10 family can only execute 32-bit EL0 when in high
> + * p-states. Pretend it does not support 32-bit EL0.
> + */
> + if (is_midr_in_range_list(read_cpuid_id(), bad_aarch32_el0)) {
> + struct arm64_ftr_reg *regp;
> +
> + regp = get_arm64_ftr_reg(SYS_ID_AA64PFR0_EL1);
> + if (!regp)
> + return;
> + u64 val = (regp->sys_val & ~ID_AA64PFR0_EL1_EL0_MASK)
> + | ID_AA64PFR0_EL1_EL0_IMP;
> +
> + update_cpu_ftr_reg(regp, val);
> + }
> +}
> +
> static void __init setup_system_capabilities(void)
> {
> /*
> @@ -3562,6 +3587,8 @@ static void __init setup_system_capabilities(void)
>
> void __init setup_system_features(void)
> {
> + bad_aarch32_el0_fixup();
> +
> setup_system_capabilities();
>
> kpti_install_ng_mappings();
Nick Chan
next prev parent reply other threads:[~2024-09-16 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 9:09 [PATCH v2 0/2] Disable 32-bit EL0 for Apple A10(X), T2 Nick Chan
2024-09-09 9:09 ` [PATCH v2 1/2] arm64: cputype: Add CPU types for A7-A11, T2 SoCs Nick Chan
2024-09-09 9:10 ` [PATCH v2 2/2] arm64: cpufeature: Pretend that Apple A10 family does not support 32-bit EL0 Nick Chan
2024-09-16 13:41 ` Nick Chan [this message]
2024-09-16 15:30 ` Catalin Marinas
2024-09-16 16:00 ` Nick Chan
2024-09-16 16:24 ` 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=f908c9ca-8063-44f4-b534-ddfc067b98c2@gmail.com \
--to=towinchenmi@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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