* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > + .quad 0x00cf9a000000ffff /* boot: 4GB code at 0x00000000 */
> > + .quad 0x00cf92000000ffff /* boot: 4GB data at 0x00000000 */
> > .quad 0x0000000000000000 /* 0x20 unused */
> > .quad 0x0000000000000000 /* 0x28 unused */
> > .quad 0x0000000000000000 /* 0x33 TLS entry 1 */
>
> actually, the reason for the small boot GDT was that some systems
> wouldnt even boot with a larger GDT. (there was some BIOS interaction,
> forgot what it was - iirc it was mach-visws and also some other older
> box)
>
> the 'simplification' you do here is actually how Linux worked before
> it was fixed for those systems.
>
> so i'd be quite nervous to touch this area of the GDT code. (I'd
> support a renaming though, gdt_table is indeed ugly.)
and this seems to have a ripple effect on the rest of your GDT changes -
i'll wait for this to be cleared before doing a line by line review of
them. I commented on the mostly-unaffected ones already.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
