From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving physical memory at boot time
Date: Thu, 06 Mar 2003 15:24:11 -0800 [thread overview]
Message-ID: <3E67D89B.1010308@zytor.com> (raw)
In-Reply-To: <20030306212607.GA173@elf.ucw.cz>
Pavel Machek wrote:
>
> 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?]
>
If you pass mem= you have to pass mem=3840M. Yes, it sucks, but if you
genuinely have a machine which is so fucked up that you can't rely on
the memory map the BIOS presents to you, you have problems to begin with.
Oh yes, this is why GRUB passing the mem= parameter gratuitously was
beyond total and complete brainfuckage.
-hpa
next prev parent reply other threads:[~2003-03-06 23:13 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
2003-03-06 23:24 ` H. Peter Anvin [this message]
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=3E67D89B.1010308@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).