Reserving a fixed physical address page of RAM.
Quoted 32 lines · Jon Ringle
Quoted 2 lines · Fawad Lateef
Quoted 1 line · Jon Ringle
Do you think that the following would work to properly
reserve the
Quoted 1 line
Quoted 1 line
memory. If it does, then I think I can just do a
ioremap(0x0ffff000,
Quoted 1 line
Quoted 1 line
0x1000) to obtain a virtual address. (Ofcourse I wouldactually use
Quoted 4 lines
Quoted 4 lines
symbolic names rather than the hardcoded addesses shown here).
Index:
linux/arch/arm/mm/init.c===================================================================
Quoted 4 lines
Quoted 1 line
---
linux.orig/arch/arm/mm/init.c2006-11-3011:03:00.000000000
Quoted 2 lines
-0500
+++linux/arch/arm/mm/init.c2006-11-3011:09:09.000000000 -0500
Quoted 4 lines
Quoted 4 lines
(quoted diff) +0
-0@@ -429,6 +429,10 @@ unsigned long addr; void *vectors;Quoted 10 lines
Review line 437
Quoted 8 lines
(quoted diff) +3
-0+#ifdef CONFIG_MACH_VERTICAL_RSC4 + reserve_bootmem (0x0ffff000, 0x1000); #endif + /* * Allocate the vector page early. */I think you can do like this but can't say accurately
Quoted 7 lines
because I havn't
Quoted 3 lines
worked on arm architecture and also you havn't mentioned your kernel-version or function (in file
arch/arm/mm/init.c) which you are going to do callreserve_bootmem!Kernel version is 2.6.16.29 and the
reserve_bootmem()call above is at the top of the functiondevicemaps_init().
Is there some way I can verify that the above works? I've tried the following to try to get info on the reservation:
# cat /proc/iomem # cat /proc/meminfo # cat /proc/slabinfo # echo m > /proc/sysrq-trigger
The only one that hints that this might have worked is the echo m > /proc/sysrq-trigger in that I see the reserved pages count one larger than using a kernel without this patch. Does this mean that the page I reserved won't get used by Linux for any purpose?
Jon
Quoted 2 lines · Jon Ringle
Quoted 1 line · Jon Ringle
Fawad Lateef wrote:
<snip>
Quoted 38 lines
Quoted 23 lines
Quoted 3 lines
Quoted 3 lines
Index:
linux/arch/arm/mm/init.c===================================================================
Quoted 4 lines
Quoted 1 line
---
linux.orig/arch/arm/mm/init.c2006-11-3011:03:00.000000000
Quoted 2 lines
-0500
+++linux/arch/arm/mm/init.c2006-11-3011:09:09.000000000 -0500
Quoted 4 lines
Quoted 4 lines
(quoted diff) +0
-0@@ -429,6 +429,10 @@ unsigned long addr; void *vectors;Quoted 10 lines
Review line 437
Quoted 8 lines
(quoted diff) +3
-0+#ifdef CONFIG_MACH_VERTICAL_RSC4 + reserve_bootmem (0x0ffff000, 0x1000); #endif + /* * Allocate the vector page early. */I think you can do like this but can't say accurately
Quoted 7 lines
because I havn't
Quoted 3 lines
worked on arm architecture and also you havn't mentioned your kernel-version or function (in file
arch/arm/mm/init.c) which you are going to do callreserve_bootmem!Kernel version is 2.6.16.29 and the
reserve_bootmem()call above is at the top of the functiondevicemaps_init().Is there some way I can verify that the above works? I've tried the following to try to get info on the reservation:
# cat /proc/iomem # cat /proc/meminfo # cat /proc/slabinfo # echo m > /proc/sysrq-trigger
Quoted 5 lines
The only one that hints that this might have worked is the
echo m > /proc/sysrq-triggerin that I see the reserved pages count one larger than using a kernel without this patch. Does this mean that the page I reserved won't get used by Linux for any purpose?
I havn't looked at " # echo m /proc/sysrq-trigger" till now but I am almost sure that it will reserve/work because calling reserve_bootmem internally sets the bit representing physical memory page (CMIIW).
Signature · 1 line
Fawad Lateef