arm64: Use a variable to store non-global mappings decision

Browse source

Refactor the code which checks to see if we need to use non-global
mappings to use a variable instead of checking with the CPU capabilities
each time, doing the initial check for KPTI early in boot before we
start allocating memory so we still avoid transitioning to non-global
mappings in common cases.

Since this variable always matches our decision about non-global
mappings this means we can also combine arm64_kernel_use_ng_mappings()
and arm64_unmap_kernel_at_el0() into a single function, the variable
simply stores the result and the decision code is elsewhere. We could
just have the users check the variable directly but having a function
makes it clear that these uses are read-only.

The result is that we simplify the code a bit and reduces the amount of
code executed at runtime.

Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Will Deacon <will@kernel.org>

...

This commit is contained in:

Mark Brown 2019-12-09 18:12:17 +00:00 • committed by Will Deacon

parent 92ac6fd162

commit 09e3c22a86

4 changed files with 65 additions and 88 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

87

arch/arm64/include/asm/mmu.h

View file

4

arch/arm64/include/asm/pgtable-prot.h

View file

55

arch/arm64/kernel/cpufeature.c

View file

7

arch/arm64/kernel/setup.c

View file