lkml.org 
[lkml]   [2018]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 2/3] arm64: cpufeature: Fix handling of CTR_EL0.IDC field
From
Date
Hi,

On 04/10/18 09:33, Suzuki K Poulose wrote:
> CTR_EL0.IDC reports the data cache clean requirements for instruction
> to data coherence. However, if the field is 0, we need to check the
> CLIDR_EL1 fields to detect the status of the feature. Currently we
> don't do this and generate a warning with tainting the kernel, when
> there is a mismatch in the field among the CPUs. Also the userspace
> doesn't have a reliable way to check the CLIDR_EL1 register to check
> the status.
>
> This patch fixes the problem by checking the CLIDR_EL1 fields, when
> (CTR_EL0.IDC == 0) and updates the kernel's copy of the CTR_EL0 for
> the CPU with the actual status of the feature. This would allow the
> sanity check infrastructure to do the proper checking of the fields
> and also allow the CTR_EL0 emulation code to supply the real status
> of the feature.
>
> Now, if a CPU has raw CTR_EL0.IDC == 0 and effective IDC == 1 (with
> overall system wide IDC == 1), we need to expose the real value to
> the user. So, we trap CTR_EL0 access on the CPU which reports incorrect
> CTR_EL0.IDC.
>
> Fixes: commit 6ae4b6e057888 ("arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC")
> Cc: Shanker Donthineni <shankerd@codeaurora.org>
> Cc: Philip Elcan <pelcan@codeaurora.org>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

> static void
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index ba16bb7762ca..d3caeabf09ed 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -861,18 +861,30 @@ static bool has_cache_idc(const struct arm64_cpu_capabilities *entry,
> if (scope == SCOPE_SYSTEM)
> ctr = arm64_ftr_reg_ctrel0.sys_val;
> else
> - ctr = read_cpuid_cachetype();
> + ctr = read_cpuid_effective_cachetype();
>
> return ctr & BIT(CTR_IDC_SHIFT);
> }
>
> +static void cpu_emulate_effective_ctr(const struct arm64_cpu_capabilities *__unused)
> +{
> + /*
> + * If the CPU exposes raw CTR_EL0.IDC = 0, while effectively
> + * CTR_EL0.IDC = 1 (from CLIDR values), we need to trap accesses
> + * to the CTR_EL0 on this CPU and emulate it with the real/safe
> + * value.
> + */
> + if (!(read_cpuid_cachetype() & BIT(CTR_IDC_SHIFT)))
> + sysreg_clear_set(sctlr_el1, SCTLR_EL1_UCT, 0);
> +}
> +


> static bool has_cache_dic(const struct arm64_cpu_capabilities *entry,
> int scope)
> {
> u64 ctr;
>
> if (scope == SCOPE_SYSTEM)
> - ctr = arm64_ftr_reg_ctrel0.sys_val;
> + ctr = read_cpuid_effective_cachetype();
> else
> ctr = read_cpuid_cachetype();

I have messed this hunk in resolving the conflict with a rebase.
This should be :

if (scope == SCOPE_SYSTEM)
ctr = arm64_ftr_reg_ctrel0.sys_val;
else
- ctr = read_cpuid_cachetype();
+ ctr = read_cpuid_effective_cachetype();

I have fixed this locally for v2.

Suzuki

\
 
 \ /
  Last update: 2018-10-04 15:09    [W:0.075 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site