[Top] [All Lists]

Describing Physical RAM Map to Linux

Subject: Describing Physical RAM Map to Linux
From: h h <>
Date: Sat, 7 Apr 2007 14:59:15 -0700 (PDT)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; 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;

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.


Don't get soaked. Take a quick peek at the forecast
with theYahoo! Search weather shortcut.
<Prev in Thread] Current Thread [Next in Thread>