Mark Brown 09e3c22a86 arm64: Use a variable to store non-global mappings decision ... 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>		2020-01-15 14:11:18 +00:00
..
asm	arm64: Use a variable to store non-global mappings decision	2020-01-15 14:11:18 +00:00
uapi/asm	Merge remote-tracking branch 'kvmarm/kvm-arm64/stolen-time' into kvmarm-master/next	2019-10-24 15:04:09 +01:00