| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Describing Physical RAM Map to Linux |
| From: | h h <harsh512@yahoo.com> |
| Date: | Sat, 7 Apr 2007 14:59:15 -0700 (PDT) |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=KUbXwErGz5/XYep0feSfAgphBJo0VIOX63tguoAnmqKh5JfGFgl3HIlLEo3FI6mglqvOK6z7Fuz3GpdrRXIr0n6eGJxWSNHs3iB2H7TNM9jSk1F8bdn2m+kAS28n5cRfASwtqNejXQP51sz92YaW7+Ijn2cgkqNDhsLSiFWsIcs=; |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
|
Hi, 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? We are using 2.6.16 on Cavium/Octeon based platform. Thanks, JJ
Don't get soaked. Take a quick peek at the forecast with theYahoo! Search weather shortcut. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Back ground user process display issue on linux-2.6.18 kernel, sathesh babu |
|---|---|
| Next by Date: | [PATCH] Register PCI host bridge resource earlier, Thomas Bogendoerfer |
| Previous by Thread: | [PATCH 7/16] add Loongson processor definitions, zhangfx@lemote.com |
| Next by Thread: | Re: Describing Physical RAM Map to Linux, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |