GSoC: Correct placement and naming of memory protection APIs

Utkarsh Rai utkarsh.rai60 at gmail.com
Sat Jul 18 04:33:43 UTC 2020


Hello,
In RTEMS each set of BSP has its own MMU implementation, for utilizing this
for high-level operations such as thread-stack protection we need a common
interface that is implemented for each BSP but is available for high-level
operations ( Something along the lines of the cache manager ), my current
implementation can be viewed here
<https://github.com/ur10/rtems/blob/Thread_stack_protection/cpukit/include/rtems/score/memorymanagement.h#L64>
and
here
<https://github.com/ur10/rtems/blob/Thread_stack_protection/bsps/arm/xilinx-zynq/mmu/bsp-set-mmu-attr.c#L10>
My question is, what should be the correct placement of these APIs and
hence there naming? Can we model it based on the cache-manager
(rtems_memory_protection_xx_xx)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200718/90f3688f/attachment.html>


More information about the devel mailing list