lkml.org 
[lkml]   [2000]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: 2.3.4[67] does not boot with PAE36
Date
I guess we basically pray that the bios gods don't put this data into kernel
code/data regions? I can understand, I just want to be clear.

01009120 ? If that is hex, it is just over the 16M limit. If decimal, just
below 1M. I'm mostly curious.

If smp_find_config were incorporated into the e820 setup code, it could
easily be marked as such. If the page is read-once, it would probably be
better to mark it reserved when we are freeing pages and let the
smp_get_config() free it.

Nathan


> -----Original Message-----
> From: Ingo Molnar [mailto:mingo@chiara.csoma.elte.hu]
> Sent: Friday, February 25, 2000 3:11 PM
> To: Linus Torvalds
> Cc: Christoph Rohland; linux-kernel@vger.rutgers.edu
> Subject: Re: 2.3.4[67] does not boot with PAE36
>
>
>
> ok, how about splitting smp_scan_config() up into two pieces,
> smp_find_config() and smp_get_config():
>
> - smp_find_config() finds the config (the mpf), but does not do a
> smp_get_mpf() which dereferences the (potentially high-memory)
> pointer, only does a reserve_bootmem() on it.
>
> - paging_init() runs [which will not allocate into the mptable
> because we have reserved that 4k area]
>
> - smp_get_config() gets called, which now sees all the RAM. (this is
> already present now internally, it's called smp_get_mpf())
>
> in this context smp_find_config() is just part of the 'RAM
> configuration'
> (and e820 interpretation) process - some special reserved system areas
> have to be reserved additionally to the e820 map. In fact, if
> BIOSes were
> designed cleanly (and pigs could fly), then the SMP configuration area
> would be part of the e820 area. (eg my mpf is at 01009120
> which is marked
> as 'usable' by the e820 map.) All these special cases would
> be handled in
> a single place.
>
> this splitup should solve all these problems - any objections?
>
> Ingo
>
>
>
> -
> 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/

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.322 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site