2019-06-03 05:44:50 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-only */
|
2012-03-05 11:49:28 +00:00
|
|
|
/*
|
|
|
|
|
* Based on arch/arm/mm/proc.S
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2001 Deep Blue Solutions Ltd.
|
|
|
|
|
* Copyright (C) 2012 ARM Ltd.
|
|
|
|
|
* Author: Catalin Marinas <catalin.marinas@arm.com>
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <linux/init.h>
|
|
|
|
|
#include <linux/linkage.h>
|
2020-06-09 04:32:42 +00:00
|
|
|
#include <linux/pgtable.h>
|
2012-03-05 11:49:28 +00:00
|
|
|
#include <asm/assembler.h>
|
|
|
|
|
#include <asm/asm-offsets.h>
|
2020-03-13 09:05:01 +00:00
|
|
|
#include <asm/asm_pointer_auth.h>
|
2012-03-05 11:49:28 +00:00
|
|
|
#include <asm/hwcap.h>
|
2016-04-27 16:47:07 +00:00
|
|
|
#include <asm/pgtable-hwdef.h>
|
2016-02-25 01:44:57 +00:00
|
|
|
#include <asm/cpufeature.h>
|
|
|
|
|
#include <asm/alternative.h>
|
2020-03-13 09:04:55 +00:00
|
|
|
#include <asm/smp.h>
|
2019-09-06 09:58:01 +00:00
|
|
|
#include <asm/sysreg.h>
|
2012-03-05 11:49:28 +00:00
|
|
|
|
2014-04-02 16:55:40 +00:00
|
|
|
#ifdef CONFIG_ARM64_64K_PAGES
|
|
|
|
|
#define TCR_TG_FLAGS TCR_TG0_64K | TCR_TG1_64K
|
2015-10-19 13:19:37 +00:00
|
|
|
#elif defined(CONFIG_ARM64_16K_PAGES)
|
|
|
|
|
#define TCR_TG_FLAGS TCR_TG0_16K | TCR_TG1_16K
|
|
|
|
|
#else /* CONFIG_ARM64_4K_PAGES */
|
2014-04-02 16:55:40 +00:00
|
|
|
#define TCR_TG_FLAGS TCR_TG0_4K | TCR_TG1_4K
|
|
|
|
|
#endif
|
|
|
|
|
|
2018-02-27 14:15:49 +00:00
|
|
|
#ifdef CONFIG_RANDOMIZE_BASE
|
|
|
|
|
#define TCR_KASLR_FLAGS TCR_NFD1
|
|
|
|
|
#else
|
|
|
|
|
#define TCR_KASLR_FLAGS 0
|
|
|
|
|
#endif
|
|
|
|
|
|
2014-04-02 16:55:40 +00:00
|
|
|
#define TCR_SMP_FLAGS TCR_SHARED
|
2012-03-05 11:49:28 +00:00
|
|
|
|
2014-04-02 16:55:40 +00:00
|
|
|
/* PTWs cacheable, inner/outer WBWA */
|
|
|
|
|
#define TCR_CACHE_FLAGS TCR_IRGN_WBWA | TCR_ORGN_WBWA
|
|
|
|
|
|
2018-12-28 08:30:31 +00:00
|
|
|
#ifdef CONFIG_KASAN_SW_TAGS
|
2020-12-22 20:01:38 +00:00
|
|
|
#define TCR_KASAN_SW_FLAGS TCR_TBI1 | TCR_TBID1
|
2018-12-28 08:30:31 +00:00
|
|
|
#else
|
2020-12-22 20:01:38 +00:00
|
|
|
#define TCR_KASAN_SW_FLAGS 0
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_KASAN_HW_TAGS
|
2021-06-02 23:52:29 +00:00
|
|
|
#define TCR_MTE_FLAGS SYS_TCR_EL1_TCMA1 | TCR_TBI1 | TCR_TBID1
|
2020-12-22 20:01:38 +00:00
|
|
|
#else
|
2021-06-02 23:52:29 +00:00
|
|
|
/*
|
|
|
|
|
* The mte_zero_clear_page_tags() implementation uses DC GZVA, which relies on
|
|
|
|
|
* TBI being enabled at EL1.
|
|
|
|
|
*/
|
|
|
|
|
#define TCR_MTE_FLAGS TCR_TBI1 | TCR_TBID1
|
2018-12-28 08:30:31 +00:00
|
|
|
#endif
|
|
|
|
|
|
2019-11-27 09:51:13 +00:00
|
|
|
/*
|
|
|
|
|
* Default MAIR_EL1. MT_NORMAL_TAGGED is initially mapped as Normal memory and
|
|
|
|
|
* changed during __cpu_setup to Normal Tagged if the system supports MTE.
|
|
|
|
|
*/
|
2019-12-11 18:40:09 +00:00
|
|
|
#define MAIR_EL1_SET \
|
|
|
|
|
(MAIR_ATTRIDX(MAIR_ATTR_DEVICE_nGnRnE, MT_DEVICE_nGnRnE) | \
|
|
|
|
|
MAIR_ATTRIDX(MAIR_ATTR_DEVICE_nGnRE, MT_DEVICE_nGnRE) | \
|
|
|
|
|
MAIR_ATTRIDX(MAIR_ATTR_NORMAL_NC, MT_NORMAL_NC) | \
|
|
|
|
|
MAIR_ATTRIDX(MAIR_ATTR_NORMAL, MT_NORMAL) | \
|
2019-11-27 09:51:13 +00:00
|
|
|
MAIR_ATTRIDX(MAIR_ATTR_NORMAL, MT_NORMAL_TAGGED))
|
2012-03-05 11:49:28 +00:00
|
|
|
|
2015-01-26 18:33:44 +00:00
|
|
|
#ifdef CONFIG_CPU_PM
|
2013-07-17 09:14:45 +00:00
|
|
|
/**
|
|
|
|
|
* cpu_do_suspend - save CPU registers context
|
|
|
|
|
*
|
|
|
|
|
* x0: virtual address of context pointer
|
2020-04-27 16:00:12 +00:00
|
|
|
*
|
|
|
|
|
* This must be kept in sync with struct cpu_suspend_ctx in <asm/suspend.h>.
|
2013-07-17 09:14:45 +00:00
|
|
|
*/
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_START(cpu_do_suspend)
|
2013-07-17 09:14:45 +00:00
|
|
|
mrs x2, tpidr_el0
|
|
|
|
|
mrs x3, tpidrro_el0
|
|
|
|
|
mrs x4, contextidr_el1
|
2019-04-08 17:17:19 +00:00
|
|
|
mrs x5, osdlr_el1
|
|
|
|
|
mrs x6, cpacr_el1
|
|
|
|
|
mrs x7, tcr_el1
|
|
|
|
|
mrs x8, vbar_el1
|
|
|
|
|
mrs x9, mdscr_el1
|
|
|
|
|
mrs x10, oslsr_el1
|
|
|
|
|
mrs x11, sctlr_el1
|
2021-05-20 11:50:27 +00:00
|
|
|
get_this_cpu_offset x12
|
2019-04-08 17:17:19 +00:00
|
|
|
mrs x13, sp_el0
|
2013-07-17 09:14:45 +00:00
|
|
|
stp x2, x3, [x0]
|
2019-04-08 17:17:19 +00:00
|
|
|
stp x4, x5, [x0, #16]
|
|
|
|
|
stp x6, x7, [x0, #32]
|
|
|
|
|
stp x8, x9, [x0, #48]
|
|
|
|
|
stp x10, x11, [x0, #64]
|
|
|
|
|
stp x12, x13, [x0, #80]
|
2020-04-27 16:00:12 +00:00
|
|
|
/*
|
|
|
|
|
* Save x18 as it may be used as a platform register, e.g. by shadow
|
|
|
|
|
* call stack.
|
|
|
|
|
*/
|
|
|
|
|
str x18, [x0, #96]
|
2013-07-17 09:14:45 +00:00
|
|
|
ret
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_END(cpu_do_suspend)
|
2013-07-17 09:14:45 +00:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* cpu_do_resume - restore CPU register context
|
|
|
|
|
*
|
2016-04-27 16:47:07 +00:00
|
|
|
* x0: Address of context pointer
|
2013-07-17 09:14:45 +00:00
|
|
|
*/
|
2018-01-29 12:00:00 +00:00
|
|
|
.pushsection ".idmap.text", "awx"
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_START(cpu_do_resume)
|
2013-07-17 09:14:45 +00:00
|
|
|
ldp x2, x3, [x0]
|
|
|
|
|
ldp x4, x5, [x0, #16]
|
2016-04-27 16:47:07 +00:00
|
|
|
ldp x6, x8, [x0, #32]
|
|
|
|
|
ldp x9, x10, [x0, #48]
|
|
|
|
|
ldp x11, x12, [x0, #64]
|
2016-11-03 20:23:09 +00:00
|
|
|
ldp x13, x14, [x0, #80]
|
2020-04-27 16:00:12 +00:00
|
|
|
/*
|
|
|
|
|
* Restore x18, as it may be used as a platform register, and clear
|
|
|
|
|
* the buffer to minimize the risk of exposure when used for shadow
|
|
|
|
|
* call stack.
|
|
|
|
|
*/
|
|
|
|
|
ldr x18, [x0, #96]
|
|
|
|
|
str xzr, [x0, #96]
|
2013-07-17 09:14:45 +00:00
|
|
|
msr tpidr_el0, x2
|
|
|
|
|
msr tpidrro_el0, x3
|
|
|
|
|
msr contextidr_el1, x4
|
|
|
|
|
msr cpacr_el1, x6
|
2016-04-27 16:47:07 +00:00
|
|
|
|
|
|
|
|
/* Don't change t0sz here, mask those bits when restoring */
|
2019-04-08 17:17:19 +00:00
|
|
|
mrs x7, tcr_el1
|
|
|
|
|
bfi x8, x7, TCR_T0SZ_OFFSET, TCR_TxSZ_WIDTH
|
2016-04-27 16:47:07 +00:00
|
|
|
|
2013-07-17 09:14:45 +00:00
|
|
|
msr tcr_el1, x8
|
|
|
|
|
msr vbar_el1, x9
|
2016-08-26 15:03:42 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* __cpu_setup() cleared MDSCR_EL1.MDE and friends, before unmasking
|
|
|
|
|
* debug exceptions. By restoring MDSCR_EL1 here, we may take a debug
|
2017-11-02 12:12:34 +00:00
|
|
|
* exception. Mask them until local_daif_restore() in cpu_suspend()
|
2016-08-26 15:03:42 +00:00
|
|
|
* resets them.
|
|
|
|
|
*/
|
2017-11-02 12:12:34 +00:00
|
|
|
disable_daif
|
2013-07-17 09:14:45 +00:00
|
|
|
msr mdscr_el1, x10
|
2016-08-26 15:03:42 +00:00
|
|
|
|
2016-04-27 16:47:07 +00:00
|
|
|
msr sctlr_el1, x12
|
2021-05-20 11:50:27 +00:00
|
|
|
set_this_cpu_offset x13
|
2016-11-03 20:23:09 +00:00
|
|
|
msr sp_el0, x14
|
2013-07-17 09:14:45 +00:00
|
|
|
/*
|
|
|
|
|
* Restore oslsr_el1 by writing oslar_el1
|
|
|
|
|
*/
|
2019-04-08 17:17:19 +00:00
|
|
|
msr osdlr_el1, x5
|
2013-07-17 09:14:45 +00:00
|
|
|
ubfx x11, x11, #1, #1
|
|
|
|
|
msr oslar_el1, x11
|
2016-01-13 14:50:03 +00:00
|
|
|
reset_pmuserenr_el0 x0 // Disable PMU access from EL0
|
2020-03-05 09:06:22 +00:00
|
|
|
reset_amuserenr_el0 x0 // Disable AMU access from EL0
|
2018-01-15 19:38:59 +00:00
|
|
|
|
|
|
|
|
alternative_if ARM64_HAS_RAS_EXTN
|
|
|
|
|
msr_s SYS_DISR_EL1, xzr
|
|
|
|
|
alternative_else_nop_endif
|
|
|
|
|
|
2020-04-23 10:16:05 +00:00
|
|
|
ptrauth_keys_install_kernel_nosync x14, x1, x2, x3
|
2013-07-17 09:14:45 +00:00
|
|
|
isb
|
|
|
|
|
ret
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_END(cpu_do_resume)
|
2016-08-24 17:27:29 +00:00
|
|
|
.popsection
|
2013-07-17 09:14:45 +00:00
|
|
|
#endif
|
|
|
|
|
|
2018-01-29 12:00:00 +00:00
|
|
|
.pushsection ".idmap.text", "awx"
|
2018-02-06 22:22:50 +00:00
|
|
|
|
|
|
|
|
.macro __idmap_cpu_set_reserved_ttbr1, tmp1, tmp2
|
2020-11-03 10:22:29 +00:00
|
|
|
adrp \tmp1, reserved_pg_dir
|
2018-01-29 11:59:57 +00:00
|
|
|
phys_to_ttbr \tmp2, \tmp1
|
2019-08-07 15:55:19 +00:00
|
|
|
offset_ttbr1 \tmp2, \tmp1
|
2018-02-06 22:22:50 +00:00
|
|
|
msr ttbr1_el1, \tmp2
|
|
|
|
|
isb
|
|
|
|
|
tlbi vmalle1
|
|
|
|
|
dsb nsh
|
|
|
|
|
isb
|
|
|
|
|
.endm
|
|
|
|
|
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
/*
|
2018-07-31 13:08:56 +00:00
|
|
|
* void idmap_cpu_replace_ttbr1(phys_addr_t ttbr1)
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
*
|
|
|
|
|
* This is the low-level counterpart to cpu_replace_ttbr1, and should not be
|
|
|
|
|
* called by anything else. It can only be executed from a TTBR0 mapping.
|
|
|
|
|
*/
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_START(idmap_cpu_replace_ttbr1)
|
2017-11-02 12:12:34 +00:00
|
|
|
save_and_disable_daif flags=x2
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
|
2018-02-06 22:22:50 +00:00
|
|
|
__idmap_cpu_set_reserved_ttbr1 x1, x3
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
|
2019-08-07 15:55:19 +00:00
|
|
|
offset_ttbr1 x0, x3
|
2018-07-31 13:08:56 +00:00
|
|
|
msr ttbr1_el1, x0
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
isb
|
|
|
|
|
|
2017-11-02 12:12:34 +00:00
|
|
|
restore_daif x2
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
|
|
|
|
|
ret
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_END(idmap_cpu_replace_ttbr1)
|
arm64: mm: add code to safely replace TTBR1_EL1
If page tables are modified without suitable TLB maintenance, the ARM
architecture permits multiple TLB entries to be allocated for the same
VA. When this occurs, it is permitted that TLB conflict aborts are
raised in response to synchronous data/instruction accesses, and/or and
amalgamation of the TLB entries may be used as a result of a TLB lookup.
The presence of conflicting TLB entries may result in a variety of
behaviours detrimental to the system (e.g. erroneous physical addresses
may be used by I-cache fetches and/or page table walks). Some of these
cases may result in unexpected changes of hardware state, and/or result
in the (asynchronous) delivery of SError.
To avoid these issues, we must avoid situations where conflicting
entries may be allocated into TLBs. For user and module mappings we can
follow a strict break-before-make approach, but this cannot work for
modifications to the swapper page tables that cover the kernel text and
data.
Instead, this patch adds code which is intended to be executed from the
idmap, which can safely unmap the swapper page tables as it only
requires the idmap to be active. This enables us to uninstall the active
TTBR1_EL1 entry, invalidate TLBs, then install a new TTBR1_EL1 entry
without potentially unmapping code or data required for the sequence.
This avoids the risk of conflict, but requires that updates are staged
in a copy of the swapper page tables prior to being installed.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-01-25 11:45:01 +00:00
|
|
|
.popsection
|
|
|
|
|
|
2018-02-06 22:22:50 +00:00
|
|
|
#ifdef CONFIG_UNMAP_KERNEL_AT_EL0
|
2018-01-29 12:00:00 +00:00
|
|
|
.pushsection ".idmap.text", "awx"
|
2018-02-06 22:22:50 +00:00
|
|
|
|
|
|
|
|
.macro __idmap_kpti_get_pgtable_ent, type
|
|
|
|
|
dc cvac, cur_\()\type\()p // Ensure any existing dirty
|
|
|
|
|
dmb sy // lines are written back before
|
|
|
|
|
ldr \type, [cur_\()\type\()p] // loading the entry
|
2018-02-13 13:14:09 +00:00
|
|
|
tbz \type, #0, skip_\()\type // Skip invalid and
|
|
|
|
|
tbnz \type, #11, skip_\()\type // non-global entries
|
2018-02-06 22:22:50 +00:00
|
|
|
.endm
|
|
|
|
|
|
|
|
|
|
.macro __idmap_kpti_put_pgtable_ent_ng, type
|
|
|
|
|
orr \type, \type, #PTE_NG // Same bit for blocks and pages
|
2018-06-22 15:23:45 +00:00
|
|
|
str \type, [cur_\()\type\()p] // Update the entry and ensure
|
|
|
|
|
dmb sy // that it is visible to all
|
|
|
|
|
dc civac, cur_\()\type\()p // CPUs.
|
2018-02-06 22:22:50 +00:00
|
|
|
.endm
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* void __kpti_install_ng_mappings(int cpu, int num_cpus, phys_addr_t swapper)
|
|
|
|
|
*
|
|
|
|
|
* Called exactly once from stop_machine context by each CPU found during boot.
|
|
|
|
|
*/
|
|
|
|
|
__idmap_kpti_flag:
|
|
|
|
|
.long 1
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_START(idmap_kpti_install_ng_mappings)
|
2018-02-06 22:22:50 +00:00
|
|
|
cpu .req w0
|
|
|
|
|
num_cpus .req w1
|
|
|
|
|
swapper_pa .req x2
|
|
|
|
|
swapper_ttb .req x3
|
|
|
|
|
flag_ptr .req x4
|
|
|
|
|
cur_pgdp .req x5
|
|
|
|
|
end_pgdp .req x6
|
|
|
|
|
pgd .req x7
|
|
|
|
|
cur_pudp .req x8
|
|
|
|
|
end_pudp .req x9
|
|
|
|
|
pud .req x10
|
|
|
|
|
cur_pmdp .req x11
|
|
|
|
|
end_pmdp .req x12
|
|
|
|
|
pmd .req x13
|
|
|
|
|
cur_ptep .req x14
|
|
|
|
|
end_ptep .req x15
|
|
|
|
|
pte .req x16
|
|
|
|
|
|
|
|
|
|
mrs swapper_ttb, ttbr1_el1
|
arm64: mm: Offset TTBR1 to allow 52-bit PTRS_PER_PGD
Enabling 52-bit VAs on arm64 requires that the PGD table expands from 64
entries (for the 48-bit case) to 1024 entries. This quantity,
PTRS_PER_PGD is used as follows to compute which PGD entry corresponds
to a given virtual address, addr:
pgd_index(addr) -> (addr >> PGDIR_SHIFT) & (PTRS_PER_PGD - 1)
Userspace addresses are prefixed by 0's, so for a 48-bit userspace
address, uva, the following is true:
(uva >> PGDIR_SHIFT) & (1024 - 1) == (uva >> PGDIR_SHIFT) & (64 - 1)
In other words, a 48-bit userspace address will have the same pgd_index
when using PTRS_PER_PGD = 64 and 1024.
Kernel addresses are prefixed by 1's so, given a 48-bit kernel address,
kva, we have the following inequality:
(kva >> PGDIR_SHIFT) & (1024 - 1) != (kva >> PGDIR_SHIFT) & (64 - 1)
In other words a 48-bit kernel virtual address will have a different
pgd_index when using PTRS_PER_PGD = 64 and 1024.
If, however, we note that:
kva = 0xFFFF << 48 + lower (where lower[63:48] == 0b)
and, PGDIR_SHIFT = 42 (as we are dealing with 64KB PAGE_SIZE)
We can consider:
(kva >> PGDIR_SHIFT) & (1024 - 1) - (kva >> PGDIR_SHIFT) & (64 - 1)
= (0xFFFF << 6) & 0x3FF - (0xFFFF << 6) & 0x3F // "lower" cancels out
= 0x3C0
In other words, one can switch PTRS_PER_PGD to the 52-bit value globally
provided that they increment ttbr1_el1 by 0x3C0 * 8 = 0x1E00 bytes when
running with 48-bit kernel VAs (TCR_EL1.T1SZ = 16).
For kernel configuration where 52-bit userspace VAs are possible, this
patch offsets ttbr1_el1 and sets PTRS_PER_PGD corresponding to the
52-bit value.
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Suggested-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Steve Capper <steve.capper@arm.com>
[will: added comment to TTBR1_BADDR_4852_OFFSET calculation]
Signed-off-by: Will Deacon <will.deacon@arm.com>
2018-12-06 22:50:39 +00:00
|
|
|
restore_ttbr1 swapper_ttb
|
2018-02-06 22:22:50 +00:00
|
|
|
adr flag_ptr, __idmap_kpti_flag
|
|
|
|
|
|
|
|
|
|
cbnz cpu, __idmap_kpti_secondary
|
|
|
|
|
|
|
|
|
|
/* We're the boot CPU. Wait for the others to catch up */
|
|
|
|
|
sevl
|
|
|
|
|
1: wfe
|
2019-12-06 22:13:37 +00:00
|
|
|
ldaxr w17, [flag_ptr]
|
|
|
|
|
eor w17, w17, num_cpus
|
|
|
|
|
cbnz w17, 1b
|
2018-02-06 22:22:50 +00:00
|
|
|
|
|
|
|
|
/* We need to walk swapper, so turn off the MMU. */
|
|
|
|
|
pre_disable_mmu_workaround
|
2019-12-06 22:13:37 +00:00
|
|
|
mrs x17, sctlr_el1
|
|
|
|
|
bic x17, x17, #SCTLR_ELx_M
|
|
|
|
|
msr sctlr_el1, x17
|
2018-02-06 22:22:50 +00:00
|
|
|
isb
|
|
|
|
|
|
|
|
|
|
/* Everybody is enjoying the idmap, so we can rewrite swapper. */
|
|
|
|
|
/* PGD */
|
|
|
|
|
mov cur_pgdp, swapper_pa
|
|
|
|
|
add end_pgdp, cur_pgdp, #(PTRS_PER_PGD * 8)
|
|
|
|
|
do_pgd: __idmap_kpti_get_pgtable_ent pgd
|
|
|
|
|
tbnz pgd, #1, walk_puds
|
|
|
|
|
next_pgd:
|
2018-02-13 13:14:09 +00:00
|
|
|
__idmap_kpti_put_pgtable_ent_ng pgd
|
|
|
|
|
skip_pgd:
|
2018-02-06 22:22:50 +00:00
|
|
|
add cur_pgdp, cur_pgdp, #8
|
|
|
|
|
cmp cur_pgdp, end_pgdp
|
|
|
|
|
b.ne do_pgd
|
|
|
|
|
|
|
|
|
|
/* Publish the updated tables and nuke all the TLBs */
|
|
|
|
|
dsb sy
|
|
|
|
|
tlbi vmalle1is
|
|
|
|
|
dsb ish
|
|
|
|
|
isb
|
|
|
|
|
|
|
|
|
|
/* We're done: fire up the MMU again */
|
2019-12-06 22:13:37 +00:00
|
|
|
mrs x17, sctlr_el1
|
|
|
|
|
orr x17, x17, #SCTLR_ELx_M
|
2021-02-08 09:57:12 +00:00
|
|
|
set_sctlr_el1 x17
|
2019-08-27 17:12:57 +00:00
|
|
|
|
2018-02-06 22:22:50 +00:00
|
|
|
/* Set the flag to zero to indicate that we're all done */
|
|
|
|
|
str wzr, [flag_ptr]
|
|
|
|
|
ret
|
|
|
|
|
|
|
|
|
|
/* PUD */
|
|
|
|
|
walk_puds:
|
|
|
|
|
.if CONFIG_PGTABLE_LEVELS > 3
|
|
|
|
|
pte_to_phys cur_pudp, pgd
|
|
|
|
|
add end_pudp, cur_pudp, #(PTRS_PER_PUD * 8)
|
|
|
|
|
do_pud: __idmap_kpti_get_pgtable_ent pud
|
|
|
|
|
tbnz pud, #1, walk_pmds
|
|
|
|
|
next_pud:
|
2018-02-13 13:14:09 +00:00
|
|
|
__idmap_kpti_put_pgtable_ent_ng pud
|
|
|
|
|
skip_pud:
|
2018-02-06 22:22:50 +00:00
|
|
|
add cur_pudp, cur_pudp, 8
|
|
|
|
|
cmp cur_pudp, end_pudp
|
|
|
|
|
b.ne do_pud
|
|
|
|
|
b next_pgd
|
|
|
|
|
.else /* CONFIG_PGTABLE_LEVELS <= 3 */
|
|
|
|
|
mov pud, pgd
|
|
|
|
|
b walk_pmds
|
|
|
|
|
next_pud:
|
|
|
|
|
b next_pgd
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
/* PMD */
|
|
|
|
|
walk_pmds:
|
|
|
|
|
.if CONFIG_PGTABLE_LEVELS > 2
|
|
|
|
|
pte_to_phys cur_pmdp, pud
|
|
|
|
|
add end_pmdp, cur_pmdp, #(PTRS_PER_PMD * 8)
|
|
|
|
|
do_pmd: __idmap_kpti_get_pgtable_ent pmd
|
|
|
|
|
tbnz pmd, #1, walk_ptes
|
|
|
|
|
next_pmd:
|
2018-02-13 13:14:09 +00:00
|
|
|
__idmap_kpti_put_pgtable_ent_ng pmd
|
|
|
|
|
skip_pmd:
|
2018-02-06 22:22:50 +00:00
|
|
|
add cur_pmdp, cur_pmdp, #8
|
|
|
|
|
cmp cur_pmdp, end_pmdp
|
|
|
|
|
b.ne do_pmd
|
|
|
|
|
b next_pud
|
|
|
|
|
.else /* CONFIG_PGTABLE_LEVELS <= 2 */
|
|
|
|
|
mov pmd, pud
|
|
|
|
|
b walk_ptes
|
|
|
|
|
next_pmd:
|
|
|
|
|
b next_pud
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
/* PTE */
|
|
|
|
|
walk_ptes:
|
|
|
|
|
pte_to_phys cur_ptep, pmd
|
|
|
|
|
add end_ptep, cur_ptep, #(PTRS_PER_PTE * 8)
|
|
|
|
|
do_pte: __idmap_kpti_get_pgtable_ent pte
|
|
|
|
|
__idmap_kpti_put_pgtable_ent_ng pte
|
2018-02-13 13:14:09 +00:00
|
|
|
skip_pte:
|
2018-02-06 22:22:50 +00:00
|
|
|
add cur_ptep, cur_ptep, #8
|
|
|
|
|
cmp cur_ptep, end_ptep
|
|
|
|
|
b.ne do_pte
|
|
|
|
|
b next_pmd
|
|
|
|
|
|
2019-12-06 22:13:37 +00:00
|
|
|
.unreq cpu
|
|
|
|
|
.unreq num_cpus
|
|
|
|
|
.unreq swapper_pa
|
|
|
|
|
.unreq cur_pgdp
|
|
|
|
|
.unreq end_pgdp
|
|
|
|
|
.unreq pgd
|
|
|
|
|
.unreq cur_pudp
|
|
|
|
|
.unreq end_pudp
|
|
|
|
|
.unreq pud
|
|
|
|
|
.unreq cur_pmdp
|
|
|
|
|
.unreq end_pmdp
|
|
|
|
|
.unreq pmd
|
|
|
|
|
.unreq cur_ptep
|
|
|
|
|
.unreq end_ptep
|
|
|
|
|
.unreq pte
|
|
|
|
|
|
2018-02-06 22:22:50 +00:00
|
|
|
/* Secondary CPUs end up here */
|
|
|
|
|
__idmap_kpti_secondary:
|
|
|
|
|
/* Uninstall swapper before surgery begins */
|
2019-12-06 22:13:37 +00:00
|
|
|
__idmap_cpu_set_reserved_ttbr1 x16, x17
|
2018-02-06 22:22:50 +00:00
|
|
|
|
|
|
|
|
/* Increment the flag to let the boot CPU we're ready */
|
2019-12-06 22:13:37 +00:00
|
|
|
1: ldxr w16, [flag_ptr]
|
|
|
|
|
add w16, w16, #1
|
|
|
|
|
stxr w17, w16, [flag_ptr]
|
2018-02-06 22:22:50 +00:00
|
|
|
cbnz w17, 1b
|
|
|
|
|
|
|
|
|
|
/* Wait for the boot CPU to finish messing around with swapper */
|
|
|
|
|
sevl
|
|
|
|
|
1: wfe
|
2019-12-06 22:13:37 +00:00
|
|
|
ldxr w16, [flag_ptr]
|
|
|
|
|
cbnz w16, 1b
|
2018-02-06 22:22:50 +00:00
|
|
|
|
|
|
|
|
/* All done, act like nothing happened */
|
2019-12-06 22:13:37 +00:00
|
|
|
offset_ttbr1 swapper_ttb, x16
|
2018-02-06 22:22:50 +00:00
|
|
|
msr ttbr1_el1, swapper_ttb
|
|
|
|
|
isb
|
|
|
|
|
ret
|
|
|
|
|
|
|
|
|
|
.unreq swapper_ttb
|
|
|
|
|
.unreq flag_ptr
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_END(idmap_kpti_install_ng_mappings)
|
2018-02-06 22:22:50 +00:00
|
|
|
.popsection
|
|
|
|
|
#endif
|
|
|
|
|
|
2012-03-05 11:49:28 +00:00
|
|
|
/*
|
|
|
|
|
* __cpu_setup
|
|
|
|
|
*
|
2020-03-13 09:04:52 +00:00
|
|
|
* Initialise the processor for turning the MMU on.
|
|
|
|
|
*
|
|
|
|
|
* Output:
|
|
|
|
|
* Return in x0 the value of the SCTLR_EL1 register.
|
2012-03-05 11:49:28 +00:00
|
|
|
*/
|
2018-01-29 12:00:00 +00:00
|
|
|
.pushsection ".idmap.text", "awx"
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_START(__cpu_setup)
|
2015-10-06 17:46:22 +00:00
|
|
|
tlbi vmalle1 // Invalidate local TLB
|
|
|
|
|
dsb nsh
|
2012-03-05 11:49:28 +00:00
|
|
|
|
2020-03-13 09:04:52 +00:00
|
|
|
mov x1, #3 << 20
|
|
|
|
|
msr cpacr_el1, x1 // Enable FP/ASIMD
|
|
|
|
|
mov x1, #1 << 12 // Reset mdscr_el1 and disable
|
|
|
|
|
msr mdscr_el1, x1 // access to the DCC from EL0
|
arm64: debug: unmask PSTATE.D earlier
Clearing PSTATE.D is one of the requirements for generating a debug
exception. The arm64 booting protocol requires that PSTATE.D is set,
since many of the debug registers (for example, the hw_breakpoint
registers) are UNKNOWN out of reset and could potentially generate
spurious, fatal debug exceptions in early boot code if PSTATE.D was
clear. Once the debug registers have been safely initialised, PSTATE.D
is cleared, however this is currently broken for two reasons:
(1) The boot CPU clears PSTATE.D in a postcore_initcall and secondary
CPUs clear PSTATE.D in secondary_start_kernel. Since the initcall
runs after SMP (and the scheduler) have been initialised, there is
no guarantee that it is actually running on the boot CPU. In this
case, the boot CPU is left with PSTATE.D set and is not capable of
generating debug exceptions.
(2) In a preemptible kernel, we may explicitly schedule on the IRQ
return path to EL1. If an IRQ occurs with PSTATE.D set in the idle
thread, then we may schedule the kthread_init thread, run the
postcore_initcall to clear PSTATE.D and then context switch back
to the idle thread before returning from the IRQ. The exception
return path will then restore PSTATE.D from the stack, and set it
again.
This patch fixes the problem by moving the clearing of PSTATE.D earlier
to proc.S. This has the desirable effect of clearing it in one place for
all CPUs, long before we have to worry about the scheduler or any
exception handling. We ensure that the previous reset of MDSCR_EL1 has
completed before unmasking the exception, so that any spurious
exceptions resulting from UNKNOWN debug registers are not generated.
Without this patch applied, the kprobes selftests have been seen to fail
under KVM, where we end up attempting to step the OOL instruction buffer
with PSTATE.D set and therefore fail to complete the step.
Cc: <stable@vger.kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Reported-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-07-19 14:07:37 +00:00
|
|
|
isb // Unmask debug exceptions now,
|
|
|
|
|
enable_dbg // since this is per-cpu
|
2020-03-13 09:04:52 +00:00
|
|
|
reset_pmuserenr_el0 x1 // Disable PMU access from EL0
|
2020-03-25 11:11:08 +00:00
|
|
|
reset_amuserenr_el0 x1 // Disable AMU access from EL0
|
2020-03-05 09:06:22 +00:00
|
|
|
|
2012-03-05 11:49:28 +00:00
|
|
|
/*
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
* Default values for VMSA control registers. These will be adjusted
|
|
|
|
|
* below depending on detected CPU features.
|
2012-03-05 11:49:28 +00:00
|
|
|
*/
|
2021-03-26 18:01:36 +00:00
|
|
|
mair .req x17
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
tcr .req x16
|
2021-03-26 18:01:36 +00:00
|
|
|
mov_q mair, MAIR_EL1_SET
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
mov_q tcr, TCR_TxSZ(VA_BITS) | TCR_CACHE_FLAGS | TCR_SMP_FLAGS | \
|
|
|
|
|
TCR_TG_FLAGS | TCR_KASLR_FLAGS | TCR_ASID16 | \
|
|
|
|
|
TCR_TBI0 | TCR_A1 | TCR_KASAN_SW_FLAGS
|
2020-12-22 20:01:38 +00:00
|
|
|
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
#ifdef CONFIG_ARM64_MTE
|
2019-09-06 09:58:01 +00:00
|
|
|
/*
|
|
|
|
|
* Update MAIR_EL1, GCR_EL1 and TFSR*_EL1 if MTE is supported
|
|
|
|
|
* (ID_AA64PFR1_EL1[11:8] > 1).
|
|
|
|
|
*/
|
|
|
|
|
mrs x10, ID_AA64PFR1_EL1
|
|
|
|
|
ubfx x10, x10, #ID_AA64PFR1_MTE_SHIFT, #4
|
|
|
|
|
cmp x10, #ID_AA64PFR1_MTE
|
|
|
|
|
b.lt 1f
|
|
|
|
|
|
|
|
|
|
/* Normal Tagged memory type at the corresponding MAIR index */
|
|
|
|
|
mov x10, #MAIR_ATTR_NORMAL_TAGGED
|
2021-03-26 18:01:36 +00:00
|
|
|
bfi mair, x10, #(8 * MT_NORMAL_TAGGED), #8
|
2019-09-06 09:58:01 +00:00
|
|
|
|
arm64: kasan: mte: use a constant kernel GCR_EL1 value
When KASAN_HW_TAGS is selected, KASAN is enabled at boot time, and the
hardware supports MTE, we'll initialize `kernel_gcr_excl` with a value
dependent on KASAN_TAG_MAX. While the resulting value is a constant
which depends on KASAN_TAG_MAX, we have to perform some runtime work to
generate the value, and have to read the value from memory during the
exception entry path. It would be better if we could generate this as a
constant at compile-time, and use it as such directly.
Early in boot within __cpu_setup(), we initialize GCR_EL1 to a safe
value, and later override this with the value required by KASAN. If
CONFIG_KASAN_HW_TAGS is not selected, or if KASAN is disabeld at boot
time, the kernel will not use IRG instructions, and so the initial value
of GCR_EL1 is does not matter to the kernel. Thus, we can instead have
__cpu_setup() initialize GCR_EL1 to a value consistent with
KASAN_TAG_MAX, and avoid the need to re-initialize it during hotplug and
resume form suspend.
This patch makes arem64 use a compile-time constant KERNEL_GCR_EL1
value, which is compatible with KASAN_HW_TAGS when this is selected.
This removes the need to re-initialize GCR_EL1 dynamically, and acts as
an optimization to the entry assembly, which no longer needs to load
this value from memory. The redundant initialization hooks are removed.
In order to do this, KASAN_TAG_MAX needs to be visible outside of the
core KASAN code. To do this, I've moved the KASAN_TAG_* values into
<linux/kasan-tags.h>.
There should be no functional change as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Peter Collingbourne <pcc@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Will Deacon <will@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Tested-by: Andrey Konovalov <andreyknvl@gmail.com>
Link: https://lore.kernel.org/r/20210714143843.56537-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-07-14 14:38:42 +00:00
|
|
|
mov x10, #KERNEL_GCR_EL1
|
2019-09-06 09:58:01 +00:00
|
|
|
msr_s SYS_GCR_EL1, x10
|
|
|
|
|
|
2021-05-07 18:59:05 +00:00
|
|
|
/*
|
|
|
|
|
* If GCR_EL1.RRND=1 is implemented the same way as RRND=0, then
|
|
|
|
|
* RGSR_EL1.SEED must be non-zero for IRG to produce
|
|
|
|
|
* pseudorandom numbers. As RGSR_EL1 is UNKNOWN out of reset, we
|
|
|
|
|
* must initialize it.
|
|
|
|
|
*/
|
|
|
|
|
mrs x10, CNTVCT_EL0
|
|
|
|
|
ands x10, x10, #SYS_RGSR_EL1_SEED_MASK
|
|
|
|
|
csinc x10, x10, xzr, ne
|
|
|
|
|
lsl x10, x10, #SYS_RGSR_EL1_SEED_SHIFT
|
|
|
|
|
msr_s SYS_RGSR_EL1, x10
|
|
|
|
|
|
2019-09-06 09:58:01 +00:00
|
|
|
/* clear any pending tag check faults in TFSR*_EL1 */
|
|
|
|
|
msr_s SYS_TFSR_EL1, xzr
|
|
|
|
|
msr_s SYS_TFSRE0_EL1, xzr
|
2020-12-22 20:01:38 +00:00
|
|
|
|
|
|
|
|
/* set the TCR_EL1 bits */
|
2021-06-02 23:52:29 +00:00
|
|
|
mov_q x10, TCR_MTE_FLAGS
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
orr tcr, tcr, x10
|
2019-09-06 09:58:01 +00:00
|
|
|
1:
|
|
|
|
|
#endif
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
tcr_clear_errata_bits tcr, x9, x5
|
2018-12-06 22:50:41 +00:00
|
|
|
|
2019-08-07 15:55:22 +00:00
|
|
|
#ifdef CONFIG_ARM64_VA_BITS_52
|
2019-08-07 15:55:23 +00:00
|
|
|
ldr_l x9, vabits_actual
|
2018-12-06 22:50:41 +00:00
|
|
|
sub x9, xzr, x9
|
|
|
|
|
add x9, x9, #64
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
tcr_set_t1sz tcr, x9
|
2018-12-06 22:50:41 +00:00
|
|
|
#else
|
|
|
|
|
ldr_l x9, idmap_t0sz
|
|
|
|
|
#endif
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
tcr_set_t0sz tcr, x9
|
arm64: mm: increase VA range of identity map
The page size and the number of translation levels, and hence the supported
virtual address range, are build-time configurables on arm64 whose optimal
values are use case dependent. However, in the current implementation, if
the system's RAM is located at a very high offset, the virtual address range
needs to reflect that merely because the identity mapping, which is only used
to enable or disable the MMU, requires the extended virtual range to map the
physical memory at an equal virtual offset.
This patch relaxes that requirement, by increasing the number of translation
levels for the identity mapping only, and only when actually needed, i.e.,
when system RAM's offset is found to be out of reach at runtime.
Tested-by: Laura Abbott <lauraa@codeaurora.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2015-03-19 16:42:27 +00:00
|
|
|
|
2014-03-07 08:49:25 +00:00
|
|
|
/*
|
2017-12-13 17:07:17 +00:00
|
|
|
* Set the IPS bits in TCR_EL1.
|
2014-03-07 08:49:25 +00:00
|
|
|
*/
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
tcr_compute_pa_size tcr, #TCR_IPS_SHIFT, x5, x6
|
2015-07-10 16:24:28 +00:00
|
|
|
#ifdef CONFIG_ARM64_HW_AFDBM
|
|
|
|
|
/*
|
2018-03-26 14:12:48 +00:00
|
|
|
* Enable hardware update of the Access Flags bit.
|
|
|
|
|
* Hardware dirty bit management is enabled later,
|
|
|
|
|
* via capabilities.
|
2015-07-10 16:24:28 +00:00
|
|
|
*/
|
|
|
|
|
mrs x9, ID_AA64MMFR1_EL1
|
|
|
|
|
and x9, x9, #0xf
|
2018-03-26 14:12:48 +00:00
|
|
|
cbz x9, 1f
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
orr tcr, tcr, #TCR_HA // hardware Access flag update
|
2018-03-26 14:12:48 +00:00
|
|
|
1:
|
2015-07-10 16:24:28 +00:00
|
|
|
#endif /* CONFIG_ARM64_HW_AFDBM */
|
2021-03-26 18:01:36 +00:00
|
|
|
msr mair_el1, mair
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
msr tcr_el1, tcr
|
2020-03-13 09:04:52 +00:00
|
|
|
/*
|
|
|
|
|
* Prepare SCTLR
|
|
|
|
|
*/
|
2020-11-13 12:49:24 +00:00
|
|
|
mov_q x0, INIT_SCTLR_EL1_MMU_ON
|
2012-03-05 11:49:28 +00:00
|
|
|
ret // return to head.S
|
2021-03-26 18:01:36 +00:00
|
|
|
|
|
|
|
|
.unreq mair
|
arm64: setup: name `tcr` register
In __cpu_setup we conditionally manipulate the TCR_EL1 value in x10
after previously using x10 as a scratch register for unrelated temporary
variables.
To make this a bit clearer, let's move the TCR_EL1 value into a named
register `tcr`. To simplify the register allocation, this is placed in
the highest available caller-saved scratch register, tcr.
Following the example of `mair`, we initialise the register with the
default value prior to any feature discovery, and write it to MAIR_EL1
after all feature discovery is complete, which allows us to simplify the
featuere discovery code.
The existing `mte_tcr` register is no longer needed, and is replaced by
the use of x10 as a temporary, matching the rest of the MTE feature
discovery assembly in __cpu_setup. As x20 is no longer used, the
function is now AAPCS compliant, as we've generally aimed for in our
assembly functions.
There should be no functional change as as a result of this patch.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20210326180137.43119-3-mark.rutland@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2021-03-26 18:01:37 +00:00
|
|
|
.unreq tcr
|
2020-01-06 19:58:18 +00:00
|
|
|
SYM_FUNC_END(__cpu_setup)
|