diff options
author | Jian J Wang <jian.j.wang@intel.com> | 2017-11-28 21:49:31 +0800 |
---|---|---|
committer | Star Zeng <star.zeng@intel.com> | 2017-12-12 10:14:51 +0800 |
commit | 2ac1730bf2a51d6d0483347a0218e1768d6d7992 (patch) | |
tree | d06a91ee4cebe1fb1e692481aa9decac9f251f0c /UefiCpuPkg/CpuDxe/CpuPageTable.h | |
parent | 34e18d1758980d2a01a4503e2be6c06eba59c6ec (diff) | |
download | edk2-2ac1730bf2a51d6d0483347a0218e1768d6d7992.tar.gz edk2-2ac1730bf2a51d6d0483347a0218e1768d6d7992.tar.bz2 edk2-2ac1730bf2a51d6d0483347a0218e1768d6d7992.zip |
MdeModulePkg/DxeIpl: Mark page table as read-only
This patch will set the memory pages used for page table as read-only
memory after the paging is setup. CR0.WP must set to let it take into
effect.
A simple page table memory management mechanism, page table pool concept,
is introduced to simplify the page table memory allocation and protection.
It will also help to reduce the potential recursive "split" action during
updating memory paging attributes.
The basic idea is to allocate a bunch of continuous pages of memory in
advance as one or more page table pools, and all future page tables
consumption will happen in those pool instead of system memory. If the page
pool is reserved at the boundary of 2MB page and with same size of 2MB page,
there's no page granularity "split" operation will be needed, because the
memory of new page tables (if needed) will be usually in the same page as
target page table you're working on.
And since we have centralized page tables (a few 2MB pages), it's easier
to protect them by changing their attributes to be read-only once and for
all. There's no need to apply the protection for new page tables any more
as long as the pool has free pages available.
Once current page table pool has been used up, one can allocate another 2MB
memory pool and just set this new 2MB memory block to be read-only instead of
setting the new page tables one page by one page.
Two new PCDs PcdPageTablePoolUnitSize and PcdPageTablePoolAlignment are used
to specify the size and alignment for page table pool. For IA32 processor
0x200000 (2MB) is the only choice for both of them to meet the requirement of
page table pool.
Laszlo (lersek@redhat.com) did a regression test on QEMU virtual platform with
one middle version of this series patch. The details can be found at
https://lists.01.org/pipermail/edk2-devel/2017-December/018625.html
There're a few changes after his work.
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Star Zeng <star.zeng@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Diffstat (limited to 'UefiCpuPkg/CpuDxe/CpuPageTable.h')
0 files changed, 0 insertions, 0 deletions