MPTABLE in LinuxBIOS is put from 0x20, if the system has too many cpu and devices (slots) the mptable will get bigger than 0x464, so it will use 0x40:67.... We need to put mptable to [0xf0000:0x100000] together with acpi tables. and if it is bigger than 64k, then we have to put it on special postion ...from 1K, and pass the posstion of mptable to the kernel via command line. I will update the code in LinuxBIOS. Thanks YH - 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/
- Follow-Ups:
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: [email protected] (Eric W. Biederman)
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- References:
- RE: Inclusion of x86_64 memorize ioapic at bootup patch
- From: "Lu, Yinghai" <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: [email protected] (Eric W. Biederman)
- RE: Inclusion of x86_64 memorize ioapic at bootup patch
- Prev by Date: [PATCH 13/24] m68kspkr: register with driver core as a platfrom device
- Next by Date: Re: Platform device matching, & weird strncmp usage
- Previous by thread: Re: Inclusion of x86_64 memorize ioapic at bootup patch
- Next by thread: Re: Inclusion of x86_64 memorize ioapic at bootup patch
- Index(es):
 |