From: Ralf Baechle <ralf@linux-mips.org>
To: h h <harsh512@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Describing Physical RAM Map to Linux
Date: Mon, 9 Apr 2007 01:11:30 +0200 [thread overview]
Message-ID: <20070408231130.GA31563@linux-mips.org> (raw)
In-Reply-To: <640437.41507.qm@web53812.mail.re2.yahoo.com>
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
next prev parent reply other threads:[~2007-04-08 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 21:59 Describing Physical RAM Map to Linux h h
2007-04-08 23:11 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-10 0:31 h h
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070408231130.GA31563@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=harsh512@yahoo.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox