[PATCH 1/6] libmm-score-api. The high-level libmm API should be used by applications. It helps developers to manage memory by setting generic and target-independent protection and cache attributes for a region that has a start address, length, and desired memory attributes.

[Chris Johns]

Gedare Bloom wrote:
>>
>> What is the use case and benefit of this libmm?  Currently I see some
>> low-level changes, but what is the application or kernel level use case?
>>
> The immediate goal would be to support POSIX mprotect on BSPs that can
> (and to ignore it on those that don't). Other benefits may come in the
> future, as we can consider how real-time memory protection might be
> employed by applications.
>
> Currently we do not need this high-level interface, until mprotect shows up.
>

Dynamically loaded code could use it. The RTL code has support for 
custom allocators to allow code to be loaded and then configured as 
read-only/execute. There will be systems that will have requirements on 
loaded code being protected in this way.

Chris