diff options
| author | Ard Biesheuvel <ardb@kernel.org> | 2023-09-12 07:24:29 +0000 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2023-09-12 10:20:27 +0000 |
| commit | 4f4a2c3b0768cd389c8f27ec77871887ba89e6f5 (patch) | |
| tree | abbe6bfb2a913209f2aaafcb8c5ba5fd79a19f49 /ArmPkg/Include | |
| parent | b7a48bed16dd75ce6a864540ab7dc38d8f1f657b (diff) | |
| download | edk2-4f4a2c3b0768cd389c8f27ec77871887ba89e6f5.tar.gz edk2-4f4a2c3b0768cd389c8f27ec77871887ba89e6f5.tar.bz2 edk2-4f4a2c3b0768cd389c8f27ec77871887ba89e6f5.zip | |
ArmPkg/ArmMmuLib: Drop buggy secure memory type check
Jake reports that the IS_ARM_MEMORY_REGION_ATTRIBUTES_SECURE() macro is
no longer accurate since commit 852227a9d52e3cb9 ("ArmPkg/Mmu: Remove
handling of NONSECURE memory regions").
Fortunately, it only affects the NS bit in level 1 short descriptors,
which is ignored when executing in non-secure mode. And given that
running UEFI in the secure world is not a use case we aim to support,
let's just drop this logic altogether.
Reported-by: Jake Garver <jake@nvidia.com>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Reviewed-by: Leif Lindholm <quic_llindhol@quicinc.com>
Diffstat (limited to 'ArmPkg/Include')
| -rw-r--r-- | ArmPkg/Include/Library/ArmLib.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/ArmPkg/Include/Library/ArmLib.h b/ArmPkg/Include/Library/ArmLib.h index fb1ae57b35..6c5315d7f4 100644 --- a/ArmPkg/Include/Library/ArmLib.h +++ b/ArmPkg/Include/Library/ArmLib.h @@ -45,8 +45,6 @@ typedef enum { ARM_MEMORY_REGION_ATTRIBUTE_DEVICE,
} ARM_MEMORY_REGION_ATTRIBUTES;
-#define IS_ARM_MEMORY_REGION_ATTRIBUTES_SECURE(attr) ((UINT32)(attr) & 1)
-
typedef struct {
EFI_PHYSICAL_ADDRESS PhysicalBase;
EFI_VIRTUAL_ADDRESS VirtualBase;
|