Re: Reserving physical memory at boot time

From: H. Peter Anvin (hpa@zytor.com)
Date: Wed Mar 05 2003 - 00:44:32 EST

Next message: Theodore Ts'o: "[PATCH] Fix ext3 htree / NFS compatibility problems"
Previous message: Andrew Morton: "Re: reducing stack usage in v4l?"
Next in thread: Randy.Dunlap: "Re: Reserving physical memory at boot time"
Reply: Randy.Dunlap: "Re: Reserving physical memory at boot time"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Theodore Ts'o: "[PATCH] Fix ext3 htree / NFS compatibility problems"
Previous message: Andrew Morton: "Re: reducing stack usage in v4l?"
Next in thread: Randy.Dunlap: "Re: Reserving physical memory at boot time"
Reply: Randy.Dunlap: "Re: Reserving physical memory at boot time"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Mar 07 2003 - 22:00:27 EST