[Top] [All Lists]

Re: Describing Physical RAM Map to Linux

Subject: Re: Describing Physical RAM Map to Linux
From: h h <>
Date: Mon, 9 Apr 2007 17:31:46 -0700 (PDT)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=Message-ID:X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NUAg+sRncJRDBwv7gXLTunNYhCaci75i3uPq4j02NZZmo6rcDJFK0bY5vPBUv39bKREvTq3rkHn7HvBIxL9ehykFwp0V5m4vlubQZnkvWfEM/0bw7qIEg2qG0X/Yd9lA9BadtWh/tRJa8VbBx9l+5qPSg93M63gt9UJBLDiHY0w= ;
Original-recipient: rfc822;

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?

Ralf wrote:
The kernel does this automatically.


Sorry I don't quite understand -- What does kernel do
How does kernel automatically know how much RAM is

If you mean kernel automatically reserves the memory
it is loaded in, my question is where is this being
done? I am expecting calls to alloc_bootmem or
reserve_bootmem with addresses for text/data/stack
regions of kernel, but I don't see them.

Any pointers would be appreciated.


Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
<Prev in Thread] Current Thread [Next in Thread>