diff options
| author | Dongyan Qian <qiandongyan@loongson.cn> | 2026-06-09 14:41:36 +0300 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2026-06-10 11:13:27 +0300 |
| commit | f17ed80f61487a19271c218f7b569163e83d26eb (patch) | |
| tree | ff63ac5c8c2c927b3b24265353a6e91bd78eaa8d /BaseTools/Source/Python/Workspace/MetaFileParser.py | |
| parent | 48fa937f46db100cbb9667bce1d522dc178a192b (diff) | |
| download | edk2-f17ed80f61487a19271c218f7b569163e83d26eb.tar.xz | |
UefiCpuPkg/LoongArch64: Support NULL pointer detection
Add the LoongArch64 CPU-side support needed to make NULL pointer
detection effective after DXE page tables are established.
The platform memory map can reserve page 0, but DXE still needs the
CPU/MMU layer to enforce the requested memory attribute. Apply
EFI_MEMORY_RP to virtual address 0 after the CPU Arch protocol is
installed when PcdNullPointerDetectionPropertyMask BIT0 is enabled.
This updates the active DXE mapping after GCD setup.
Also update the LoongArch64 page-table attribute conversion path so a
requested no-read mapping clears PAGE_VALID. On the tested
LoongArchVirt/QEMU path, the no-read attribute alone does not reliably
raise a load fault for VA 0. Invalidating the PTE makes an assembly
load from address 0 raise a page-invalid load exception instead of
silently reading through the mapping.
This commit only changes the common LoongArch64 CPU/MMU support. The
LoongArchVirt platform memory-map policy is updated separately.
Signed-off-by: Dongyan Qian <qiandongyan@loongson.cn>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/MetaFileParser.py')
0 files changed, 0 insertions, 0 deletions
