2014-03-04 08:10:04 +07:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2014 Linaro Ltd. <ard.biesheuvel@linaro.org>
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __ASM_CPUFEATURE_H
|
|
|
|
#define __ASM_CPUFEATURE_H
|
|
|
|
|
2016-11-04 01:34:34 +07:00
|
|
|
#include <asm/cpucaps.h>
|
2017-10-31 22:51:10 +07:00
|
|
|
#include <asm/fpsimd.h>
|
2014-03-04 08:10:04 +07:00
|
|
|
#include <asm/hwcap.h>
|
2017-10-31 22:51:10 +07:00
|
|
|
#include <asm/sigcontext.h>
|
2015-10-19 20:24:42 +07:00
|
|
|
#include <asm/sysreg.h>
|
2014-03-04 08:10:04 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* In the arm64 world (as in the ARM world), elf_hwcap is used both internally
|
|
|
|
* in the kernel and for user space to keep track of which optional features
|
|
|
|
* are supported by the current system. So let's map feature 'x' to HWCAP_x.
|
|
|
|
* Note that HWCAP_x constants are bit fields so we need to take the log.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define MAX_CPU_FEATURES (8 * sizeof(elf_hwcap))
|
|
|
|
#define cpu_feature(x) ilog2(HWCAP_ ## x)
|
|
|
|
|
2014-11-14 22:54:10 +07:00
|
|
|
#ifndef __ASSEMBLY__
|
2014-11-14 22:54:07 +07:00
|
|
|
|
2016-11-08 20:56:20 +07:00
|
|
|
#include <linux/bug.h>
|
|
|
|
#include <linux/jump_label.h>
|
2015-05-01 00:55:50 +07:00
|
|
|
#include <linux/kernel.h>
|
|
|
|
|
2017-01-10 00:28:27 +07:00
|
|
|
/*
|
|
|
|
* CPU feature register tracking
|
|
|
|
*
|
|
|
|
* The safe value of a CPUID feature field is dependent on the implications
|
|
|
|
* of the values assigned to it by the architecture. Based on the relationship
|
|
|
|
* between the values, the features are classified into 3 types - LOWER_SAFE,
|
|
|
|
* HIGHER_SAFE and EXACT.
|
|
|
|
*
|
|
|
|
* The lowest value of all the CPUs is chosen for LOWER_SAFE and highest
|
|
|
|
* for HIGHER_SAFE. It is expected that all CPUs have the same value for
|
|
|
|
* a field when EXACT is specified, failing which, the safe value specified
|
|
|
|
* in the table is chosen.
|
|
|
|
*/
|
|
|
|
|
2015-10-19 20:24:45 +07:00
|
|
|
enum ftr_type {
|
|
|
|
FTR_EXACT, /* Use a predefined safe value */
|
|
|
|
FTR_LOWER_SAFE, /* Smaller value is safe */
|
|
|
|
FTR_HIGHER_SAFE,/* Bigger value is safe */
|
|
|
|
};
|
|
|
|
|
|
|
|
#define FTR_STRICT true /* SANITY check strict matching required */
|
|
|
|
#define FTR_NONSTRICT false /* SANITY check ignored */
|
|
|
|
|
2015-11-19 00:08:57 +07:00
|
|
|
#define FTR_SIGNED true /* Value should be treated as signed */
|
|
|
|
#define FTR_UNSIGNED false /* Value should be treated as unsigned */
|
|
|
|
|
2017-01-10 00:28:30 +07:00
|
|
|
#define FTR_VISIBLE true /* Feature visible to the user space */
|
|
|
|
#define FTR_HIDDEN false /* Feature is hidden from the user */
|
|
|
|
|
2017-12-14 21:03:44 +07:00
|
|
|
#define FTR_VISIBLE_IF_IS_ENABLED(config) \
|
|
|
|
(IS_ENABLED(config) ? FTR_VISIBLE : FTR_HIDDEN)
|
|
|
|
|
2015-10-19 20:24:45 +07:00
|
|
|
struct arm64_ftr_bits {
|
2015-11-19 00:08:57 +07:00
|
|
|
bool sign; /* Value is signed ? */
|
2017-01-10 00:28:30 +07:00
|
|
|
bool visible;
|
2015-11-19 00:08:57 +07:00
|
|
|
bool strict; /* CPU Sanity check: strict matching required ? */
|
2015-10-19 20:24:45 +07:00
|
|
|
enum ftr_type type;
|
|
|
|
u8 shift;
|
|
|
|
u8 width;
|
2016-09-09 20:07:08 +07:00
|
|
|
s64 safe_val; /* safe value for FTR_EXACT features */
|
2015-10-19 20:24:45 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* @arm64_ftr_reg - Feature register
|
|
|
|
* @strict_mask Bits which should match across all CPUs for sanity.
|
|
|
|
* @sys_val Safe value across the CPUs (system view)
|
|
|
|
*/
|
|
|
|
struct arm64_ftr_reg {
|
2016-08-31 17:31:08 +07:00
|
|
|
const char *name;
|
|
|
|
u64 strict_mask;
|
2017-01-10 00:28:30 +07:00
|
|
|
u64 user_mask;
|
2016-08-31 17:31:08 +07:00
|
|
|
u64 sys_val;
|
2017-01-10 00:28:30 +07:00
|
|
|
u64 user_val;
|
2016-08-31 17:31:08 +07:00
|
|
|
const struct arm64_ftr_bits *ftr_bits;
|
2015-10-19 20:24:45 +07:00
|
|
|
};
|
|
|
|
|
2016-08-31 17:31:10 +07:00
|
|
|
extern struct arm64_ftr_reg arm64_ftr_reg_ctrel0;
|
|
|
|
|
2016-04-22 18:25:31 +07:00
|
|
|
/* scope of capability check */
|
|
|
|
enum {
|
|
|
|
SCOPE_SYSTEM,
|
|
|
|
SCOPE_LOCAL_CPU,
|
|
|
|
};
|
|
|
|
|
2015-03-27 20:09:23 +07:00
|
|
|
struct arm64_cpu_capabilities {
|
|
|
|
const char *desc;
|
|
|
|
u16 capability;
|
2016-04-22 18:25:31 +07:00
|
|
|
int def_scope; /* default scope */
|
|
|
|
bool (*matches)(const struct arm64_cpu_capabilities *caps, int scope);
|
2016-10-18 17:27:46 +07:00
|
|
|
int (*enable)(void *); /* Called on all active CPUs */
|
2015-03-27 20:09:23 +07:00
|
|
|
union {
|
|
|
|
struct { /* To be used for erratum handling only */
|
|
|
|
u32 midr_model;
|
|
|
|
u32 midr_range_min, midr_range_max;
|
|
|
|
};
|
2015-06-12 18:06:36 +07:00
|
|
|
|
|
|
|
struct { /* Feature register checking */
|
2015-10-19 20:24:51 +07:00
|
|
|
u32 sys_reg;
|
2016-01-26 17:58:15 +07:00
|
|
|
u8 field_pos;
|
|
|
|
u8 min_field_value;
|
|
|
|
u8 hwcap_type;
|
|
|
|
bool sign;
|
2015-10-19 20:24:52 +07:00
|
|
|
unsigned long hwcap;
|
2015-06-12 18:06:36 +07:00
|
|
|
};
|
2015-03-27 20:09:23 +07:00
|
|
|
};
|
|
|
|
};
|
|
|
|
|
arm64: Provide a namespace to NCAPS
Building arm64.allmodconfig leads to the following warning:
usb/gadget/function/f_ncm.c:203:0: warning: "NCAPS" redefined
#define NCAPS (USB_CDC_NCM_NCAP_ETH_FILTER | USB_CDC_NCM_NCAP_CRC_MODE)
^
In file included from /home/build/work/batch/arch/arm64/include/asm/io.h:32:0,
from /home/build/work/batch/include/linux/clocksource.h:19,
from /home/build/work/batch/include/clocksource/arm_arch_timer.h:19,
from /home/build/work/batch/arch/arm64/include/asm/arch_timer.h:27,
from /home/build/work/batch/arch/arm64/include/asm/timex.h:19,
from /home/build/work/batch/include/linux/timex.h:65,
from /home/build/work/batch/include/linux/sched.h:19,
from /home/build/work/batch/arch/arm64/include/asm/compat.h:25,
from /home/build/work/batch/arch/arm64/include/asm/stat.h:23,
from /home/build/work/batch/include/linux/stat.h:5,
from /home/build/work/batch/include/linux/module.h:10,
from /home/build/work/batch/drivers/usb/gadget/function/f_ncm.c:19:
arch/arm64/include/asm/cpufeature.h:27:0: note: this is the location of the previous definition
#define NCAPS 2
So add a ARM64 prefix to avoid such problem.
Reported-by: Olof's autobuilder <build@lixom.net>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2014-12-04 08:17:01 +07:00
|
|
|
extern DECLARE_BITMAP(cpu_hwcaps, ARM64_NCAPS);
|
2016-09-06 00:25:48 +07:00
|
|
|
extern struct static_key_false cpu_hwcap_keys[ARM64_NCAPS];
|
arm64/cpufeature: don't use mutex in bringup path
Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which
must take the jump_label mutex.
We call cpus_set_cap() in the secondary bringup path, from the idle
thread where interrupts are disabled. Taking a mutex in this path "is a
NONO" regardless of whether it's contended, and something we must avoid.
We didn't spot this until recently, as ___might_sleep() won't warn for
this case until all CPUs have been brought up.
This patch avoids taking the mutex in the secondary bringup path. The
poking of static keys is deferred until enable_cpu_capabilities(), which
runs in a suitable context on the boot CPU. To account for the static
keys being set later, cpus_have_const_cap() is updated to use another
static key to check whether the const cap keys have been initialised,
falling back to the caps bitmap until this is the case.
This means that users of cpus_have_const_cap() gain should only gain a
single additional NOP in the fast path once the const caps are
initialised, but should always see the current cap value.
The hyp code should never dereference the caps array, since the caps are
initialized before we run the module initcall to initialise hyp. A check
is added to the hyp init code to document this requirement.
This change will sidestep a number of issues when the upcoming hotplug
locking rework is merged.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Marc Zyniger <marc.zyngier@arm.com>
Reviewed-by: Suzuki Poulose <suzuki.poulose@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Cc: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Sewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2017-05-16 21:18:05 +07:00
|
|
|
extern struct static_key_false arm64_const_caps_ready;
|
2014-11-14 22:54:07 +07:00
|
|
|
|
2016-04-22 18:25:32 +07:00
|
|
|
bool this_cpu_has_cap(unsigned int cap);
|
|
|
|
|
2014-03-04 08:10:04 +07:00
|
|
|
static inline bool cpu_have_feature(unsigned int num)
|
|
|
|
{
|
|
|
|
return elf_hwcap & (1UL << num);
|
|
|
|
}
|
|
|
|
|
2016-11-08 20:56:20 +07:00
|
|
|
/* System capability check for constant caps */
|
arm64/cpufeature: don't use mutex in bringup path
Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which
must take the jump_label mutex.
We call cpus_set_cap() in the secondary bringup path, from the idle
thread where interrupts are disabled. Taking a mutex in this path "is a
NONO" regardless of whether it's contended, and something we must avoid.
We didn't spot this until recently, as ___might_sleep() won't warn for
this case until all CPUs have been brought up.
This patch avoids taking the mutex in the secondary bringup path. The
poking of static keys is deferred until enable_cpu_capabilities(), which
runs in a suitable context on the boot CPU. To account for the static
keys being set later, cpus_have_const_cap() is updated to use another
static key to check whether the const cap keys have been initialised,
falling back to the caps bitmap until this is the case.
This means that users of cpus_have_const_cap() gain should only gain a
single additional NOP in the fast path once the const caps are
initialised, but should always see the current cap value.
The hyp code should never dereference the caps array, since the caps are
initialized before we run the module initcall to initialise hyp. A check
is added to the hyp init code to document this requirement.
This change will sidestep a number of issues when the upcoming hotplug
locking rework is merged.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Marc Zyniger <marc.zyngier@arm.com>
Reviewed-by: Suzuki Poulose <suzuki.poulose@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Cc: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Sewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2017-05-16 21:18:05 +07:00
|
|
|
static inline bool __cpus_have_const_cap(int num)
|
2016-11-08 20:56:20 +07:00
|
|
|
{
|
|
|
|
if (num >= ARM64_NCAPS)
|
|
|
|
return false;
|
|
|
|
return static_branch_unlikely(&cpu_hwcap_keys[num]);
|
|
|
|
}
|
|
|
|
|
2014-11-14 22:54:07 +07:00
|
|
|
static inline bool cpus_have_cap(unsigned int num)
|
|
|
|
{
|
arm64: Provide a namespace to NCAPS
Building arm64.allmodconfig leads to the following warning:
usb/gadget/function/f_ncm.c:203:0: warning: "NCAPS" redefined
#define NCAPS (USB_CDC_NCM_NCAP_ETH_FILTER | USB_CDC_NCM_NCAP_CRC_MODE)
^
In file included from /home/build/work/batch/arch/arm64/include/asm/io.h:32:0,
from /home/build/work/batch/include/linux/clocksource.h:19,
from /home/build/work/batch/include/clocksource/arm_arch_timer.h:19,
from /home/build/work/batch/arch/arm64/include/asm/arch_timer.h:27,
from /home/build/work/batch/arch/arm64/include/asm/timex.h:19,
from /home/build/work/batch/include/linux/timex.h:65,
from /home/build/work/batch/include/linux/sched.h:19,
from /home/build/work/batch/arch/arm64/include/asm/compat.h:25,
from /home/build/work/batch/arch/arm64/include/asm/stat.h:23,
from /home/build/work/batch/include/linux/stat.h:5,
from /home/build/work/batch/include/linux/module.h:10,
from /home/build/work/batch/drivers/usb/gadget/function/f_ncm.c:19:
arch/arm64/include/asm/cpufeature.h:27:0: note: this is the location of the previous definition
#define NCAPS 2
So add a ARM64 prefix to avoid such problem.
Reported-by: Olof's autobuilder <build@lixom.net>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2014-12-04 08:17:01 +07:00
|
|
|
if (num >= ARM64_NCAPS)
|
2014-11-14 22:54:07 +07:00
|
|
|
return false;
|
2016-11-08 20:56:20 +07:00
|
|
|
return test_bit(num, cpu_hwcaps);
|
2014-11-14 22:54:07 +07:00
|
|
|
}
|
|
|
|
|
arm64/cpufeature: don't use mutex in bringup path
Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which
must take the jump_label mutex.
We call cpus_set_cap() in the secondary bringup path, from the idle
thread where interrupts are disabled. Taking a mutex in this path "is a
NONO" regardless of whether it's contended, and something we must avoid.
We didn't spot this until recently, as ___might_sleep() won't warn for
this case until all CPUs have been brought up.
This patch avoids taking the mutex in the secondary bringup path. The
poking of static keys is deferred until enable_cpu_capabilities(), which
runs in a suitable context on the boot CPU. To account for the static
keys being set later, cpus_have_const_cap() is updated to use another
static key to check whether the const cap keys have been initialised,
falling back to the caps bitmap until this is the case.
This means that users of cpus_have_const_cap() gain should only gain a
single additional NOP in the fast path once the const caps are
initialised, but should always see the current cap value.
The hyp code should never dereference the caps array, since the caps are
initialized before we run the module initcall to initialise hyp. A check
is added to the hyp init code to document this requirement.
This change will sidestep a number of issues when the upcoming hotplug
locking rework is merged.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Marc Zyniger <marc.zyngier@arm.com>
Reviewed-by: Suzuki Poulose <suzuki.poulose@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Cc: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Sewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2017-05-16 21:18:05 +07:00
|
|
|
static inline bool cpus_have_const_cap(int num)
|
|
|
|
{
|
|
|
|
if (static_branch_likely(&arm64_const_caps_ready))
|
|
|
|
return __cpus_have_const_cap(num);
|
|
|
|
else
|
|
|
|
return cpus_have_cap(num);
|
|
|
|
}
|
|
|
|
|
2014-11-14 22:54:07 +07:00
|
|
|
static inline void cpus_set_cap(unsigned int num)
|
|
|
|
{
|
2016-09-06 00:25:48 +07:00
|
|
|
if (num >= ARM64_NCAPS) {
|
2014-11-14 22:54:07 +07:00
|
|
|
pr_warn("Attempt to set an illegal CPU capability (%d >= %d)\n",
|
arm64: Provide a namespace to NCAPS
Building arm64.allmodconfig leads to the following warning:
usb/gadget/function/f_ncm.c:203:0: warning: "NCAPS" redefined
#define NCAPS (USB_CDC_NCM_NCAP_ETH_FILTER | USB_CDC_NCM_NCAP_CRC_MODE)
^
In file included from /home/build/work/batch/arch/arm64/include/asm/io.h:32:0,
from /home/build/work/batch/include/linux/clocksource.h:19,
from /home/build/work/batch/include/clocksource/arm_arch_timer.h:19,
from /home/build/work/batch/arch/arm64/include/asm/arch_timer.h:27,
from /home/build/work/batch/arch/arm64/include/asm/timex.h:19,
from /home/build/work/batch/include/linux/timex.h:65,
from /home/build/work/batch/include/linux/sched.h:19,
from /home/build/work/batch/arch/arm64/include/asm/compat.h:25,
from /home/build/work/batch/arch/arm64/include/asm/stat.h:23,
from /home/build/work/batch/include/linux/stat.h:5,
from /home/build/work/batch/include/linux/module.h:10,
from /home/build/work/batch/drivers/usb/gadget/function/f_ncm.c:19:
arch/arm64/include/asm/cpufeature.h:27:0: note: this is the location of the previous definition
#define NCAPS 2
So add a ARM64 prefix to avoid such problem.
Reported-by: Olof's autobuilder <build@lixom.net>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2014-12-04 08:17:01 +07:00
|
|
|
num, ARM64_NCAPS);
|
2016-09-06 00:25:48 +07:00
|
|
|
} else {
|
2014-11-14 22:54:07 +07:00
|
|
|
__set_bit(num, cpu_hwcaps);
|
2016-09-06 00:25:48 +07:00
|
|
|
}
|
2014-11-14 22:54:07 +07:00
|
|
|
}
|
|
|
|
|
2015-10-19 20:24:44 +07:00
|
|
|
static inline int __attribute_const__
|
2016-01-26 17:58:16 +07:00
|
|
|
cpuid_feature_extract_signed_field_width(u64 features, int field, int width)
|
2015-07-21 19:23:26 +07:00
|
|
|
{
|
2015-10-19 20:24:44 +07:00
|
|
|
return (s64)(features << (64 - width - field)) >> (64 - width);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline int __attribute_const__
|
2016-01-26 17:58:16 +07:00
|
|
|
cpuid_feature_extract_signed_field(u64 features, int field)
|
2015-10-19 20:24:44 +07:00
|
|
|
{
|
2016-01-26 17:58:16 +07:00
|
|
|
return cpuid_feature_extract_signed_field_width(features, field, 4);
|
2015-07-21 19:23:26 +07:00
|
|
|
}
|
|
|
|
|
2015-11-19 00:08:56 +07:00
|
|
|
static inline unsigned int __attribute_const__
|
|
|
|
cpuid_feature_extract_unsigned_field_width(u64 features, int field, int width)
|
|
|
|
{
|
|
|
|
return (u64)(features << (64 - width - field)) >> (64 - width);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline unsigned int __attribute_const__
|
|
|
|
cpuid_feature_extract_unsigned_field(u64 features, int field)
|
|
|
|
{
|
|
|
|
return cpuid_feature_extract_unsigned_field_width(features, field, 4);
|
|
|
|
}
|
|
|
|
|
2016-08-31 17:31:08 +07:00
|
|
|
static inline u64 arm64_ftr_mask(const struct arm64_ftr_bits *ftrp)
|
2015-10-19 20:24:45 +07:00
|
|
|
{
|
|
|
|
return (u64)GENMASK(ftrp->shift + ftrp->width - 1, ftrp->shift);
|
|
|
|
}
|
|
|
|
|
2017-01-10 00:28:30 +07:00
|
|
|
static inline u64 arm64_ftr_reg_user_value(const struct arm64_ftr_reg *reg)
|
|
|
|
{
|
|
|
|
return (reg->user_val | (reg->sys_val & reg->user_mask));
|
|
|
|
}
|
|
|
|
|
2016-01-26 17:58:16 +07:00
|
|
|
static inline int __attribute_const__
|
arm64/cpufeature: check correct field width when updating sys_val
When we're updating a register's sys_val, we use arm64_ftr_value() to
find the new field value. We use cpuid_feature_extract_field() to find
the new value, but this implicitly assumes a 4-bit field, so we may
extract more bits than we mean to for fields like CTR_EL0.L1ip.
This affects update_cpu_ftr_reg(), where we may extract erroneous values
for ftr_cur and ftr_new. Depending on the additional bits extracted in
either case, we may erroneously detect that the value is mismatched, and
we'll try to compute a new safe value.
Dependent on these extra bits and feature type, arm64_ftr_safe_value()
may pessimistically select the always-safe value, or may erroneously
choose either the extracted cur or new value as the safe option. The
extra bits will subsequently be masked out in arm64_ftr_set_value(), so
we may choose a higher value, yet write back a lower one.
Fix this by passing the width down explicitly in arm64_ftr_value(), so
we always extract the correct amount.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2017-02-23 23:03:17 +07:00
|
|
|
cpuid_feature_extract_field_width(u64 features, int field, int width, bool sign)
|
2016-01-26 17:58:16 +07:00
|
|
|
{
|
|
|
|
return (sign) ?
|
arm64/cpufeature: check correct field width when updating sys_val
When we're updating a register's sys_val, we use arm64_ftr_value() to
find the new field value. We use cpuid_feature_extract_field() to find
the new value, but this implicitly assumes a 4-bit field, so we may
extract more bits than we mean to for fields like CTR_EL0.L1ip.
This affects update_cpu_ftr_reg(), where we may extract erroneous values
for ftr_cur and ftr_new. Depending on the additional bits extracted in
either case, we may erroneously detect that the value is mismatched, and
we'll try to compute a new safe value.
Dependent on these extra bits and feature type, arm64_ftr_safe_value()
may pessimistically select the always-safe value, or may erroneously
choose either the extracted cur or new value as the safe option. The
extra bits will subsequently be masked out in arm64_ftr_set_value(), so
we may choose a higher value, yet write back a lower one.
Fix this by passing the width down explicitly in arm64_ftr_value(), so
we always extract the correct amount.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2017-02-23 23:03:17 +07:00
|
|
|
cpuid_feature_extract_signed_field_width(features, field, width) :
|
|
|
|
cpuid_feature_extract_unsigned_field_width(features, field, width);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline int __attribute_const__
|
|
|
|
cpuid_feature_extract_field(u64 features, int field, bool sign)
|
|
|
|
{
|
|
|
|
return cpuid_feature_extract_field_width(features, field, 4, sign);
|
2016-01-26 17:58:16 +07:00
|
|
|
}
|
|
|
|
|
2016-08-31 17:31:08 +07:00
|
|
|
static inline s64 arm64_ftr_value(const struct arm64_ftr_bits *ftrp, u64 val)
|
2015-10-19 20:24:45 +07:00
|
|
|
{
|
arm64/cpufeature: check correct field width when updating sys_val
When we're updating a register's sys_val, we use arm64_ftr_value() to
find the new field value. We use cpuid_feature_extract_field() to find
the new value, but this implicitly assumes a 4-bit field, so we may
extract more bits than we mean to for fields like CTR_EL0.L1ip.
This affects update_cpu_ftr_reg(), where we may extract erroneous values
for ftr_cur and ftr_new. Depending on the additional bits extracted in
either case, we may erroneously detect that the value is mismatched, and
we'll try to compute a new safe value.
Dependent on these extra bits and feature type, arm64_ftr_safe_value()
may pessimistically select the always-safe value, or may erroneously
choose either the extracted cur or new value as the safe option. The
extra bits will subsequently be masked out in arm64_ftr_set_value(), so
we may choose a higher value, yet write back a lower one.
Fix this by passing the width down explicitly in arm64_ftr_value(), so
we always extract the correct amount.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2017-02-23 23:03:17 +07:00
|
|
|
return (s64)cpuid_feature_extract_field_width(val, ftrp->shift, ftrp->width, ftrp->sign);
|
2015-10-19 20:24:45 +07:00
|
|
|
}
|
|
|
|
|
2015-10-19 20:24:42 +07:00
|
|
|
static inline bool id_aa64mmfr0_mixed_endian_el0(u64 mmfr0)
|
2015-07-21 19:23:26 +07:00
|
|
|
{
|
2016-01-26 17:58:16 +07:00
|
|
|
return cpuid_feature_extract_unsigned_field(mmfr0, ID_AA64MMFR0_BIGENDEL_SHIFT) == 0x1 ||
|
|
|
|
cpuid_feature_extract_unsigned_field(mmfr0, ID_AA64MMFR0_BIGENDEL0_SHIFT) == 0x1;
|
2015-07-21 19:23:26 +07:00
|
|
|
}
|
|
|
|
|
2016-04-18 16:28:34 +07:00
|
|
|
static inline bool id_aa64pfr0_32bit_el0(u64 pfr0)
|
|
|
|
{
|
|
|
|
u32 val = cpuid_feature_extract_unsigned_field(pfr0, ID_AA64PFR0_EL0_SHIFT);
|
|
|
|
|
|
|
|
return val == ID_AA64PFR0_EL0_32BIT_64BIT;
|
|
|
|
}
|
|
|
|
|
2017-10-31 22:51:10 +07:00
|
|
|
static inline bool id_aa64pfr0_sve(u64 pfr0)
|
|
|
|
{
|
|
|
|
u32 val = cpuid_feature_extract_unsigned_field(pfr0, ID_AA64PFR0_SVE_SHIFT);
|
|
|
|
|
|
|
|
return val > 0;
|
|
|
|
}
|
|
|
|
|
2015-10-19 20:24:39 +07:00
|
|
|
void __init setup_cpu_features(void);
|
2015-07-21 19:23:26 +07:00
|
|
|
|
2015-10-19 20:24:49 +07:00
|
|
|
void update_cpu_capabilities(const struct arm64_cpu_capabilities *caps,
|
2015-03-27 20:09:23 +07:00
|
|
|
const char *info);
|
2016-06-29 00:07:30 +07:00
|
|
|
void enable_cpu_capabilities(const struct arm64_cpu_capabilities *caps);
|
2016-09-09 20:07:10 +07:00
|
|
|
void check_local_cpu_capabilities(void);
|
|
|
|
|
2016-09-09 20:07:09 +07:00
|
|
|
void update_cpu_errata_workarounds(void);
|
2016-06-29 00:07:30 +07:00
|
|
|
void __init enable_errata_workarounds(void);
|
2016-09-09 20:07:09 +07:00
|
|
|
void verify_local_cpu_errata_workarounds(void);
|
2014-11-14 22:54:09 +07:00
|
|
|
|
2017-03-23 22:14:39 +07:00
|
|
|
u64 read_sanitised_ftr_reg(u32 id);
|
2015-10-19 20:24:47 +07:00
|
|
|
|
2015-10-19 20:24:48 +07:00
|
|
|
static inline bool cpu_supports_mixed_endian_el0(void)
|
|
|
|
{
|
|
|
|
return id_aa64mmfr0_mixed_endian_el0(read_cpuid(ID_AA64MMFR0_EL1));
|
|
|
|
}
|
|
|
|
|
2016-04-18 16:28:36 +07:00
|
|
|
static inline bool system_supports_32bit_el0(void)
|
|
|
|
{
|
2016-11-08 20:56:20 +07:00
|
|
|
return cpus_have_const_cap(ARM64_HAS_32BIT_EL0);
|
2016-04-18 16:28:36 +07:00
|
|
|
}
|
|
|
|
|
2015-10-19 20:24:48 +07:00
|
|
|
static inline bool system_supports_mixed_endian_el0(void)
|
|
|
|
{
|
2017-03-23 22:14:39 +07:00
|
|
|
return id_aa64mmfr0_mixed_endian_el0(read_sanitised_ftr_reg(SYS_ID_AA64MMFR0_EL1));
|
2015-10-19 20:24:48 +07:00
|
|
|
}
|
2014-11-14 22:54:09 +07:00
|
|
|
|
2016-11-08 20:56:21 +07:00
|
|
|
static inline bool system_supports_fpsimd(void)
|
|
|
|
{
|
|
|
|
return !cpus_have_const_cap(ARM64_HAS_NO_FPSIMD);
|
|
|
|
}
|
|
|
|
|
2016-07-01 22:53:00 +07:00
|
|
|
static inline bool system_uses_ttbr0_pan(void)
|
|
|
|
{
|
|
|
|
return IS_ENABLED(CONFIG_ARM64_SW_TTBR0_PAN) &&
|
arm64: use const cap for system_uses_ttbr0_pan()
Since commit 4b65a5db362783ab ("arm64: Introduce
uaccess_{disable,enable} functionality based on TTBR0_EL1"),
system_uses_ttbr0_pan() has used cpus_have_cap() to determine whether
PAN is present.
Since commit a4023f682739439b ("arm64: Add hypervisor safe helper for
checking constant capabilities"), which was introduced around the same
time, cpus_have_cap() doesn't try to use a static key, and must always
perform a load, test, and consitional branch (likely a tbnz for the
latter two).
Elsewhere, we moved to using cpus_have_const_cap(), which can use a
static key (i.e. a non-conditional branch), which is patched at runtime
when the feature is detected.
This patch makes system_uses_ttbr0_pan() use cpus_have_const_cap(). The
static key is likely a win for hot-paths like the uacccess primitives,
and this makes our usage consistent regardless.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2017-03-11 00:44:18 +07:00
|
|
|
!cpus_have_const_cap(ARM64_HAS_PAN);
|
2016-07-01 22:53:00 +07:00
|
|
|
}
|
|
|
|
|
2017-10-31 22:51:02 +07:00
|
|
|
static inline bool system_supports_sve(void)
|
|
|
|
{
|
2017-10-31 22:51:19 +07:00
|
|
|
return IS_ENABLED(CONFIG_ARM64_SVE) &&
|
|
|
|
cpus_have_const_cap(ARM64_SVE);
|
2017-10-31 22:51:02 +07:00
|
|
|
}
|
|
|
|
|
2017-10-31 22:51:10 +07:00
|
|
|
/*
|
|
|
|
* Read the pseudo-ZCR used by cpufeatures to identify the supported SVE
|
|
|
|
* vector length.
|
|
|
|
*
|
|
|
|
* Use only if SVE is present.
|
|
|
|
* This function clobbers the SVE vector length.
|
|
|
|
*/
|
|
|
|
static inline u64 read_zcr_features(void)
|
|
|
|
{
|
|
|
|
u64 zcr;
|
|
|
|
unsigned int vq_max;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set the maximum possible VL, and write zeroes to all other
|
|
|
|
* bits to see if they stick.
|
|
|
|
*/
|
|
|
|
sve_kernel_enable(NULL);
|
|
|
|
write_sysreg_s(ZCR_ELx_LEN_MASK, SYS_ZCR_EL1);
|
|
|
|
|
|
|
|
zcr = read_sysreg_s(SYS_ZCR_EL1);
|
|
|
|
zcr &= ~(u64)ZCR_ELx_LEN_MASK; /* find sticky 1s outside LEN field */
|
|
|
|
vq_max = sve_vq_from_vl(sve_get_vl());
|
|
|
|
zcr |= vq_max - 1; /* set LEN field to maximum effective value */
|
|
|
|
|
|
|
|
return zcr;
|
|
|
|
}
|
|
|
|
|
2014-11-14 22:54:10 +07:00
|
|
|
#endif /* __ASSEMBLY__ */
|
|
|
|
|
2014-03-04 08:10:04 +07:00
|
|
|
#endif
|