summaryrefslogtreecommitdiffstats
path: root/UefiCpuPkg/Include
diff options
context:
space:
mode:
authorduntan <dun.tan@intel.com>2022-12-21 12:21:54 +0800
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2022-12-21 11:13:48 +0000
commitb822be1a20d71378b8306637e6a7ae4da449d4c8 (patch)
tree2d73d2b44480a672f9e0362bd78bf71e131d99e7 /UefiCpuPkg/Include
parent0b633b14944903c32aa061befaf38bd8d994cf13 (diff)
downloadedk2-b822be1a20d71378b8306637e6a7ae4da449d4c8.tar.gz
edk2-b822be1a20d71378b8306637e6a7ae4da449d4c8.tar.bz2
edk2-b822be1a20d71378b8306637e6a7ae4da449d4c8.zip
UefiCpuPkg/PiSmmCpuDxeSmm: Introduce page table pool mechanism
Introduce page table pool mechanism for smm page table to simplify page table memory management and protection. This mechanism has been used in DxeIpl. The basic idea is to allocate a bunch of continuous pages of memory in advance, and all future page tables consumption will happen in those pool instead of system memory. Since we have centralized page tables, we only need to mark all page table pools as RO, instead of searching page table memory layer by layer in smm page table. Once current page table pool has been used up, another memory pool will be allocated and the new pool will also be set as RO if current page table memory has been marked as RO. Signed-off-by: Dun Tan <dun.tan@intel.com> Cc: Eric Dong <eric.dong@intel.com> Reviewed-by: Ray Ni <ray.ni@intel.com> Cc: Rahul Kumar <rahul1.kumar@intel.com>
Diffstat (limited to 'UefiCpuPkg/Include')
0 files changed, 0 insertions, 0 deletions