[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250514104242.1275040-9-ardb+git@google.com>
Date: Wed, 14 May 2025 12:42:43 +0200
From: Ard Biesheuvel <ardb+git@...gle.com>
To: linux-kernel@...r.kernel.org
Cc: x86@...nel.org, Ard Biesheuvel <ardb@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, Brian Gerst <brgerst@...il.com>
Subject: [PATCH v3 0/7] x86: Robustify pgtable_l5_enabled()
From: Ard Biesheuvel <ardb@...nel.org>
This is a follow-up to the discussion at [0], broken out of that series
so we can progress while the SEV changes are being reviewed and tested.
The current implementation of pgtable_l5_enabled() is problematic
because it has two implementations, and source files need to opt into
the correct one if they contain code that might be called very early.
Other related global pseudo-constants exist that assume different values
based on the number of paging levels, and it is hard to reason about
whether or not all memory mapping and page table code is guaranteed to
observe consistent values of all of these at all times during the boot.
Case in point: currently, KASAN needs to be disabled during alternatives
patching because otherwise, it will reliably produce false positive
reports due to such inconsistencies.
This v2 drops the early variant entirely, and makes the existing late
variant, which is based on cpu_feature_enabled(), work as expected in
all cases by tweaking the CPU capability code so that it permits setting
the 5-level paging capability from assembler before calling the C
entrypoint of the core kernel.
Runtime constants were considered for PGDIR_SHIFT and PTRS_PER_P4D but
were found unsuitable as they do not support loadable modules, and so
they are replaced with expressions based on pgtable_l5_enabled(). Earlier
patching of alternatives based on CPU capabilities may be feasible, but
whether or not this improves performance is TBD. In any case, doing so
from the startup code is unlikely to be worth the added complexity.
Build and boot tested using QEMU with LA57 emulation.
Changes since v2:
- Drop first patch which has been merged
- Rename existing "la57" CPU flag to "la57_hw" and use "la57" to
indicate that 5 level paging is being used
- Move memset() out of identify_cpu()
- Make set/clear cap override arrays ro_after_init
- Split off asm-offsets update
[0] https://lore.kernel.org/all/20250504095230.2932860-28-ardb+git@google.com/
Cc: Ingo Molnar <mingo@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Brian Gerst <brgerst@...il.com>
Ard Biesheuvel (7):
x86/cpu: Use a new feature flag for 5 level paging
x86/cpu: Allow caps to be set arbitrarily early
x86/asm-offsets: Export struct cpuinfo_x86 layout for asm use
x86/boot: Set 5-level paging CPU cap before entering C code
x86/boot: Drop the early variant of pgtable_l5_enabled()
x86/boot: Drop 5-level paging related variables and early updates
x86/cpu: Make CPU capability overrides __ro_after_init
arch/x86/boot/compressed/misc.h | 8 +++---
arch/x86/boot/compressed/pgtable_64.c | 12 ---------
arch/x86/boot/startup/map_kernel.c | 21 +---------------
arch/x86/boot/startup/sme.c | 9 -------
arch/x86/include/asm/cpufeature.h | 12 ++++++---
arch/x86/include/asm/cpufeatures.h | 3 ++-
arch/x86/include/asm/page_64.h | 2 +-
arch/x86/include/asm/pgtable_64_types.h | 25 ++++---------------
arch/x86/kernel/alternative.c | 12 ---------
arch/x86/kernel/asm-offsets.c | 8 ++++++
arch/x86/kernel/asm-offsets_32.c | 9 -------
arch/x86/kernel/cpu/common.c | 26 +++-----------------
arch/x86/kernel/head64.c | 11 ---------
arch/x86/kernel/head_64.S | 15 +++++++++++
arch/x86/kvm/x86.h | 4 +--
arch/x86/mm/kasan_init_64.c | 3 ---
drivers/iommu/amd/init.c | 4 +--
drivers/iommu/intel/svm.c | 4 +--
tools/testing/selftests/kvm/x86/set_sregs_test.c | 2 +-
19 files changed, 55 insertions(+), 135 deletions(-)
base-commit: 64797551baec252f953fa8234051f88b0c368ed5
--
2.49.0.1101.gccaa498523-goog
Powered by blists - more mailing lists