Date
1 - 2 of 2
Updates on the proposal of MPU (privious sPMP)
|
bichengyang@...
Hello all,
After the discussion of the tee group, we decide to rename sPMP to MPU (the RISC-V Memory Protection Unit), and reuse page fault for MPU fault based on our discussion and feedback of the privileged group. Therefore we propose to rename page fault to MPU/MMU fault for clarity. We also have updates on the proposal of MPU: https://docs.google.com/document/d/1x7esOSBFfpcbDHaRPpe5NEWmav1_8der_nB25Hd5hqs/edit?usp=sharing Best, Bicheng |
|
|
|
Dong Du
BTW, we would like to know more opinions from privilege group and H-extension group on how MPU/sPMP and virtualization should be used together, e.g., do we have any scenarios that should use paging, MPU (sPMP), and G-stage translation together? Please feel free to give us any feedbacks to help moving forward. All the best, Dong ------------------ Original ------------------ Date: Tue, May 4, 2021 04:44 PM To: "tech-privileged"<tech-privileged@...>; "tech-tee"<tech-tee@...>; Subject: [RISC-V] [tech-privileged] Updates on the proposal of MPU (privious sPMP) Hello all,
After the discussion of the tee group, we decide to rename sPMP to MPU (the RISC-V Memory Protection Unit), and reuse page fault for MPU fault based on our discussion and feedback of the privileged group. Therefore we propose to rename page fault to MPU/MMU fault for clarity. We also have updates on the proposal of MPU: https://docs.google.com/document/d/1x7esOSBFfpcbDHaRPpe5NEWmav1_8der_nB25Hd5hqs/edit?usp=sharing Best, Bicheng |
|
|