From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reserving physical memory at boot time
Date: 4 Mar 2003 21:44:32 -0800 [thread overview]
Message-ID: <b442s0$pau$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0212040905230.8842-100000@dragon.pdx.osdl.net
Followup to: <Pine.LNX.4.33L2.0212040905230.8842-100000@dragon.pdx.osdl.net>
By author: "Randy.Dunlap" <rddunlap@osdl.org>
In newsgroup: linux.dev.kernel
>
> Patch for 'mem=exactmap' in 2.4 was submitted several weeks ago and
> Alan merged it into -ac. It does need to be pushed to Marcelo...
>
Once again, with feeling...
DON'T CALL IT mem=.
mem= is part of the boot protocol.
Call it memmap= or something, or you'll break boot loaders in weird
and subtle ways.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-03-05 5:34 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 [this message]
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
-- 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='b442s0$pau$1@cesium.transmeta.com' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.