The Wayback Machine - https://web.archive.org/web/20201106225409/https://github.com/apache/incubator-nuttx/issues/1489
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved MPU usage in PROTECTED mode #1489

Open
patacongo opened this issue Jul 30, 2020 · 0 comments
Open

Improved MPU usage in PROTECTED mode #1489

patacongo opened this issue Jul 30, 2020 · 0 comments

Comments

@patacongo
Copy link
Contributor

@patacongo patacongo commented Jul 30, 2020

In PROTECTED mode, the MPU is used to map regions of memory to supervisor- and/or user-accessible memory. Currently, that algorithm is very simple: The entire address range is made accessible in supervisor mode; a single MPU region is used to enable user-mode access in each user memory region.

Each MPU region must bit both of a power-of-two size and with an alignment in memory equal to the size. That is, a 16Kb mapped region must be aligned to a 16Kb address. This simple region mapping causes some serious memory alignment problems. For example, suppose there is 64Kb of memory (say RAM) and we need at least 1Kb for supervisor memory. At best, after the 1Kb memory is set aside for supervisor access, the remaining 63Kb can support a maximum of a 32Kb region, aligned either at the beginning of the 64Kb region or at an offset of 32Kb into the 64Kb region. The remaining 31Kb is lost.

This could be solved by either:

  1. Use multiple regions to map the memory. In the above example, we could map 48Kb with two regions (still losing 13Kb) or 56Kb with three regions (still losing 5Kb). Or, better,
  2. Use the ARMv7-M sub-regions. For example, map the entire 64Kb, but unmap the single 1Kb sub-region reserved for supervisor mode access (no memory loss).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.