Hi Laszlo,
OK.
When I discussed the CpuMmuLib API as a public API with Ray in the early days, the API recommended by Ray should be the patch 13 in this series, which only contains set/get memory region attribute, but in the first version in this series, it contains more API, one is ConfigureMmu API, which is included in ARM and RISCV versions. This API provides a interface called in PEI or DXE stage, it will configures the MMU and enables it, such as creating the page tables, filling the static page tables, cofniguring the MMU registers, enbale MMU, etc.
The paths for ARM and RISCV version APIs:
ARM: ArmPkg/Include/Library/ArmMmuLib.h
RISCV:
UefiCpuPkg/Include/Library/BaseRiscVMmuLib.h
On 3/1/24 02:26, Chao Li wrote:Hi Ray, Lazslo, This library is almost complete to refactored, it refer to ARM and RISC-V version, the API include set/get memory region attribute. I have one last question, in ARM and RISC-V version, even LoongArch old and current version, they all request a configure interface, which may be called in PEI or DXE stage, so should we open configure API? If so, it is possible for ARM RISC-V and LongArch's MMU libraries to be meged into the same instance if they wished.Sorry, I've lost all context by now. I don't understand what you mean by "they all request a configure interface". Please provide pathnames and function names for the existent code that you are referring to as examples (and then please restate / rephrase your question as well). Laszlo