Changes between Version 8 and Version 9 of Projects/MMU_Support


Ignore:
Timestamp:
May 20, 2009, 3:56:29 AM (11 years ago)
Author:
Aanjhan
Comment:

/* Mid Level APIs */

Legend:

Unmodified
Added
Removed
Modified
  • Projects/MMU_Support

    v8 v9  
    3131The middle layer of the implementation would be architecture independent. This would not just be APIs but is also the layer where the functionality of several actions are going to be present. The complete implementation can fit into the cpukit layer of RTEMS software architecture.
    3232
    33 ''' Responsibilities of this Middle Layer '''
     33One major functionality of this mid-layer is to manage the OS maintained Memory blocks and assign access attributes. These memory blocks shall be grouped by "contexts". For. E.g each task creates a "MMU Context" which points to a data structure (to be defined) of memory blocks. Each memory block then has attributes associated like "read-only", "don't execute" , "cache-inhibit", "cache-write-through" etc. There shall be APIs to generate/modify/remove these memory blocks which can be used by the higher level applications.
    3434
     35Also there shall be another set of APIs which shall be used by the low level BSP functions to extract information with respect to access rights for a particular block, the access attributes to use etc. This information will then be used by the Low level software to update/create the PTE. Also, a mechanism to inform the low level system of any invalidation/removal/change of status of a memory block is needed. This ensures that the PTE are kept upto date in case of removal of any memory areas.
    3536=  OS Maintained Memory Block (need to find a nice official name for this)  =
    3637