public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving physical memory at boot time
Date: Wed, 05 Mar 2003 07:48:38 -0800	[thread overview]
Message-ID: <3E661C56.5090503@zytor.com> (raw)
In-Reply-To: <20030305074327.673e2432.rddunlap@osdl.org>

Randy.Dunlap wrote:
> | 
> | Unfortunately last time I commented on this the response was roughly
> | "well, the patch already made it into Linus' kernel, it's too late to
> | fix it now."  That isn't exactly a very helpful response.
> 
> I don't see why it's too late.  How can it be too late?
> Ah, because it's already made it into 2.4?
> 

More because people don't want to fix their mistakes, I suspect :(

I don't know who originally started adding stuff to "mem=", but I still 
feel it needs to be backed out and renamed.

> | The mem= parameter has the semantic in the i386/PC boot protocol that
> | it specifies the top address of the usable memory region that begins
> | at 0x100000.  It's a bit of a wart that the boot loaders have to be
> | aware of this, but it's so and it's been so for a very long time.
> 
> So it's the top of the 0x100000-mem physical linear memory region
> (i.e., no gaps)?

Correct.


  reply	other threads:[~2003-03-05 15:39 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
     [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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=3E661C56.5090503@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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