From: Kunaal Mahanti <kunaal.mahanti@wipro.com>
To: Any Anderson <any_and@yahoo.com>
Cc: linux-mm@kvack.org
Subject: Re: kernel position
Date: Mon, 14 May 2001 15:19:54 +0530 (IST) [thread overview]
Message-ID: <Pine.PTX.3.96.1010514150742.26385A-100000@wipro.wipsys.sequent.com> (raw)
In-Reply-To: <20010514092219.55514.qmail@web13202.mail.yahoo.com>
On Mon, 14 May 2001, Any Anderson wrote:
Hi,
> I wann know where in the physical memory is kernel
> loaded by the loader (such as lilo) and does this
> position has any significance in mm system. If that
The kernel is loaded loaded beyond 0x1000000 (1MB), this is a h/w
constraint as most DMA devices cannot address beyond that, so we leave if
free, although there should'nt be any problem using a lower address for
kernel.
> location is to be changed which files should be
> changed. Lets assume we are talking for x86 platform.
> Thanks in advance for your time.
I think all we need is to use -Ttext flag while loading the kernel to
modify the load address. If I am correct the other things will fall in
place. mem_init() will take care of marking the remaining memory as
dynamic.
-
Kunaal Mahanti
Senior Software Engineer,
IBM NUMA-Q IDC,
Wipro Technologies.
Ph : +91-80-5732293/96 Ext: 5242
Fax: +91-80-5732296
-------------------------------------------------------------------------------
Visit us at http://www.wipro.com/ and http://www.wiproindia.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-14 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 9:22 Any Anderson
2001-05-14 9:43 ` Stephen C. Tweedie
2001-05-14 9:49 ` Kunaal Mahanti [this message]
2001-05-14 10:41 ` Stephen C. Tweedie
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=Pine.PTX.3.96.1010514150742.26385A-100000@wipro.wipsys.sequent.com \
--to=kunaal.mahanti@wipro.com \
--cc=any_and@yahoo.com \
--cc=linux-mm@kvack.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