nommu.c (48a7afe314bfc4d7f50e1608632f503dbba7e013) | nommu.c (1eeb66a1bb973534dc3d064920a5ca683823372e) |
---|---|
1/* 2 * linux/mm/nommu.c 3 * 4 * Replacement code for mm functions to support CPU's that don't 5 * have any form of memory management unit (thus no virtual memory). 6 * 7 * See Documentation/nommu-mmap.txt 8 * --- 248 unchanged lines hidden (view full) --- 257} 258 259void vunmap(void *addr) 260{ 261 BUG(); 262} 263 264/* | 1/* 2 * linux/mm/nommu.c 3 * 4 * Replacement code for mm functions to support CPU's that don't 5 * have any form of memory management unit (thus no virtual memory). 6 * 7 * See Documentation/nommu-mmap.txt 8 * --- 248 unchanged lines hidden (view full) --- 257} 258 259void vunmap(void *addr) 260{ 261 BUG(); 262} 263 264/* |
265 * Implement a stub for vmalloc_sync_all() if the architecture chose not to 266 * have one. 267 */ 268void __attribute__((weak)) vmalloc_sync_all(void) 269{ 270} 271 272/* |
|
265 * sys_brk() for the most part doesn't need the global kernel 266 * lock, except when an application is doing something nasty 267 * like trying to un-brk an area that has already been mapped 268 * to a regular file. in this case, the unmapping will need 269 * to invoke file system routines that need the global lock. 270 */ 271asmlinkage unsigned long sys_brk(unsigned long brk) 272{ --- 1105 unchanged lines hidden --- | 273 * sys_brk() for the most part doesn't need the global kernel 274 * lock, except when an application is doing something nasty 275 * like trying to un-brk an area that has already been mapped 276 * to a regular file. in this case, the unmapping will need 277 * to invoke file system routines that need the global lock. 278 */ 279asmlinkage unsigned long sys_brk(unsigned long brk) 280{ --- 1105 unchanged lines hidden --- |