1) If someone boots with their own memory map, then they must supply the
memory map.
2) If the bios gives a bogus pointer.... well, we're <insert barnyard term>
regardless, aren't we?
3) If the bios puts a ROM at the high end of memory (or maps the bios
there), then that space will be returned AddressRangeReserved, and won't be
involved. I'm only talking about AddressRangeMemory, AddressRangeACPI, and
AddressRangeNVS in the map. The latter two are necessarily used by the ACPI
drivers, so we had better support them...
Nathan
> -----Original Message-----
> From: Manfred Spraul [mailto:manfreds@colorfullife.com]
> Sent: Friday, March 03, 2000 11:45 AM
> To: Zook, Nathan
> Cc: mingo@chiara.csoma.elte.hu; x_coder@hotmail.com; sct@redhat.com;
> linux-kernel@vger.rutgers.edu
> Subject: Re: HIGH MEMORY access
>
>
> nathan.zook@amd.com wrote:
> >
> > This is changing. The new patches will be reclaim-enabled,
> so those pages
> > will be mapped, and the max_pfn-class variables will
> reflect their presence.
> >
> and what if someone boots with "mem=32M", or if the bios supplies a
> bogus pointer? or if the bios returns a pointer to a rom chip at 4 GB?
> IMHO kmap() is intended for memory that's returned from
> gfp(|GFP_HIHMEM), but not for external pointers.
>
> --
> Manfred
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Mar 07 2000 - 21:00:15 EST