diff options
| author |   Ard Biesheuvel <ardb@kernel.org> | 2022-08-02 11:00:16 +0200 |
|---|---|---|
| committer | Ard Biesheuvel <ardb@kernel.org> | 2022-11-18 09:14:08 +0100 |
| commit | 9cf42bca30e98a1c6c9e8abf876940a551eaa3d1 (patch) | |
| tree | 9f3dc73b8f91db7baefbf1d81ccefaaa1f76d29d /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | Merge tag 'efi-zboot-direct-for-v6.2' into efi/next (diff) | |
| download | wireguard-linux-9cf42bca30e98a1c6c9e8abf876940a551eaa3d1.tar.xz wireguard-linux-9cf42bca30e98a1c6c9e8abf876940a551eaa3d1.zip | |
efi: libstub: use EFI_LOADER_CODE region when moving the kernel in memory
The EFI spec is not very clear about which permissions are being given
when allocating pages of a certain type. However, it is quite obvious
that EFI_LOADER_CODE is more likely to permit execution than
EFI_LOADER_DATA, which becomes relevant once we permit booting the
kernel proper with the firmware's 1:1 mapping still active.
Ostensibly, recent systems such as the Surface Pro X grant executable
permissions to EFI_LOADER_CODE regions but not EFI_LOADER_DATA regions.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions