From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving physical memory at boot time
Date: Thu, 6 Mar 2003 22:26:07 +0100 [thread overview]
Message-ID: <20030306212607.GA173@elf.ucw.cz> (raw)
In-Reply-To: <b453mj$qpi$1@cesium.transmeta.com>
Hi!
> > OK, with feeling:
> >
> > I agree with you since the boot protocol is well-defined.
> >
> > Just to be clear, my comment was referring to
> > Documentation/kernel-parameters.txt, not to any C code.
> >
> > And it would really be helpful to catch issues like this soon
> > after they happen...
> >
>
> 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.
>
> 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.
Really? So user has to know where ACPI tables are and specify less
than that on mem= command line? That seems very
counter-intuitive. [Ahha, its probaly okay because e820 saves you.]
What do you pass on 4GB machine as mem= parameter? AFAIK those beasts
have hole at 3.75G. [Hopefully bigmem machines have working e820
tables?]
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-03-06 23:00 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
2003-03-06 21:26 ` Pavel Machek [this message]
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=20030306212607.GA173@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--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