Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-05 15:58:59 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Add on-demand paging support to ARM9 prefetch abort handler

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2860 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo
2010-08-17 01:37:39 +00:00
parent 53843efb87
commit 9567e48c57
1 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configs/README.txt
+11 -1
View File
@@ -264,13 +264,23 @@ defconfig -- This is a configuration file similar to the Linux
OS setup related to on-demand paging: OS setup related to on-demand paging:
CONFIG_PAGING - If set =y in your configation file, this setting will CONFIG_PAGING - If set =y in your configation file, this setting will
enable the on-demand paging feature as described in enable the on-demand paging feature as described in
http://www.nuttx.org/NuttXDemandPaging.html. http://www.nuttx.org/NuttXDemandPaging.html.
If CONFIG_PAGING is selected, then the following also apply: If CONFIG_PAGING is selected, then the following also apply:
CONFIG_PAGING_PAGESIZE - The size of one managed page. This must
be a value supported by the processor's memory management unit.
CONFIG_PAGING_NLOCKED - This is the number of locked pages in the
memory map. The locked address region will then be from
CONFIG_DRAM_VSTART through (CONFIG_DRAM_VSTART +
CONFIG_PAGING_PAGESIZE*CONFIG_PAGING_NLOCKED)
CONFIG_PAGING_NPAGES - The number of pages in the paged region of
the memory map. This paged region then begins at (CONFIG_DRAM_VSTART +
CONFIG_PAGING_PAGESIZE*CONFIG_PAGING_NLOCKED) and continues until
(CONFIG_DRAM_VSTART + CONFIG_PAGING_PAGESIZE*(CONFIG_PAGING_NLOCKED +
CONFIG_PAGING_NPAGES)
CONFIG_PAGING_DEFPRIO - The default, minimum priority of the page fill CONFIG_PAGING_DEFPRIO - The default, minimum priority of the page fill
worker thread. The priority of the page fill work thread will be boosted worker thread. The priority of the page fill work thread will be boosted
boosted dynmically so that it matches the priority of the task on behalf boosted dynmically so that it matches the priority of the task on behalf