linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Duncan Sands <baldrick@wanadoo.fr>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reserving physical memory at boot time
Date: Wed, 4 Dec 2002 08:25:57 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.3.95.1021204082313.23777A-100000@chaos.analogic.com> (raw)
In-Reply-To: <1038952684.11426.106.camel@irongate.swansea.linux.org.uk>

On 3 Dec 2002, Alan Cox wrote:

> On Tue, 2002-12-03 at 21:11, Richard B. Johnson wrote:
> > If you need a certain page reserved at boot-time you are out-of-luck.
> 
> Wrong - you can specify the precise memory map of a box as well as use 
> mem= to set the top of used memory. Its a painful way of marking a page
> and it only works for a page the kernel isnt loaded into.
> 

If you are refering to the "reserve=" kernel parameter, I don't
think it works for memory addresses that are inside existing RAM.
I guess if you used the "mem=" parameter to keep the kernel from
using that RAM, the combination might work, but I have never
tried it.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
   Bush : The Fourth Reich of America



  parent reply	other threads:[~2002-12-04 13:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 12:03 Reserving physical memory at boot time Duncan Sands
2002-12-03 21:11 ` Richard B. Johnson
2002-12-03 12:52   ` Duncan Sands
2002-12-03 22:14     ` Alan Cox
2002-12-03 21:58   ` Alan Cox
2002-12-03 22:18     ` bzeeb-lists
2002-12-04 13:25     ` Richard B. Johnson [this message]
     [not found]     ` <Pine.LNX.3.95.1021204082313.23777A-100000@chaos.analogic.c om>
2002-12-04 16:44       ` Mike Galbraith
2002-12-04  6:15         ` Duncan Sands
2002-12-05  5:44           ` Mike Galbraith
2002-12-04 17:01         ` Richard B. Johnson
2002-12-04 17:06           ` Randy.Dunlap
2003-03-05  5:44             ` H. Peter Anvin
2003-03-05  6:01               ` Randy.Dunlap
2003-03-05 15:04                 ` H. Peter Anvin
2003-03-05 15:43                   ` Randy.Dunlap
2003-03-05 15:48                     ` H. Peter Anvin
2003-03-06 21:26                   ` Pavel Machek
2003-03-06 23:24                     ` H. Peter Anvin
2003-03-07 23:19                       ` Pavel Machek
2003-03-09 21:08                         ` H. Peter Anvin
2003-03-09 23:07                           ` Randy.Dunlap
2002-12-03 23:23 ` James Stevenson
2002-12-04  3:53   ` Randy.Dunlap
2002-12-05  8:13 Suparna Bhattacharya

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.LNX.3.95.1021204082313.23777A-100000@chaos.analogic.com \
    --to=root@chaos.analogic.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=baldrick@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).