Re: [LinuxBIOS] Inclusion of x86_64 memorize ioapic at bootup patch

[yhlu]

does stefan put the mptable in first 1K?

good way is put mptable 0xf0000:0x100000.

YH

On 1/7/06, Eric W. Biederman  wrote:
> yhlu  writes:
> > 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....
>
> Then you or someone moved it.  The base in low memory was originally
> at 0x500, to avoid just these kinds of problems.
> > We need to put mptable to [0xf0000:0x100000] together with acpi
> > tables.
>
> Or move it up a few bytes.
> > 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.  It is always a good idea not to assign legacy regions of the
> address space new meanings.
>
> Eric
>
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

[LinuxBIOS] Inclusion of x86_64 memorize ioapic at bootup patch

yhlu  writes:
> does stefan put the mptable in first 1K?
>
> good way is put mptable 0xf0000:0x100000.

Nothing wrong with that either.  In freebios v1 when all of
that code was introduced we had a lot of boards that did
not map ram in the 0xa0000-0xfffff window.  Which is probably
why everything wound up so low.  If I recall correctly even things
that look for the linuxbios table can find it in the higher
range as well.

Regardless the important thing is not to stomp in the legacy
memory region below 0x500.

Eric