| To: | h h <harsh512@yahoo.com> |
|---|---|
| Subject: | Re: Describing Physical RAM Map to Linux |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Mon, 9 Apr 2007 01:11:30 +0200 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <640437.41507.qm@web53812.mail.re2.yahoo.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <640437.41507.qm@web53812.mail.re2.yahoo.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.2i |
On Sat, Apr 07, 2007 at 02:59:15PM -0700, h h wrote: > I have a very basic question -- When describing physical memory to the kernel > in > prom_init(), should we describe the physical memory region where kernel is > loaded or leave it out? We are using add_memory_region() call to describe > physical memory to the kernel. If we do describe the memory region where > kernel is loaded, how will kernel know not to use these pages for User > processes? The kernel does this automatically. > We are using 2.6.16 on Cavium/Octeon based platform. Which atm are only supported by Cavium's proprietary version of Linux ... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Change PCI host bridge setup/resources, Sergei Shtylyov |
|---|---|
| Next by Date: | Re: [PATCH] Register PCI host bridge resource earlier, Thomas Bogendoerfer |
| Previous by Thread: | Describing Physical RAM Map to Linux, h h |
| Next by Thread: | Re: Describing Physical RAM Map to Linux, h h |
| Indexes: | [Date] [Thread] [Top] [All Lists] |