On Feb 1, 2008 8:43 PM, Andi Kleen <andi@firstfloor.org> wrote:
quoted text
> > Section 5 and section 9.5 describe 'I/OxAPIC'. I'm not sure if it is
> > already supported by Linux, I guess it is not.
>
> I'm not sure what the point of your questions is.  Do you want to
> do something concrete or are you just interested in random buzzwords?
>
> Anyways as far as I know Linux supports the IO APICs implemented in all
> x86 chipsets fully. That is it doesn't use every possible feature they have,
> but I'm not aware of any particular limitation caused by Linux
> not supporting some IO APIC feature.
>
> The reason for the local x/APIC was that the original non x APIC did not support
> more than 8 logical CPUs being active in the system. Presumably IO xAPIC
> refers to the IO APIC without this limitation too.

APIC: 4bit
xAPIC: 8bit?
x2APIC: 32bit? 4g logical cpu?

patch from SGI for 4096cpu/512node will use apicid as 16 bits, but
actually still use only from 8 bit.
they may wait from Intel release code for x2APIC support for extend
that to 16 bit.
x2APIC will use MSR instead of MMIO to access. that is good.
we don't need to go over mptable or ACPI madt to find phyaddress for local apic.

current code could work well with 8bit local APIC, and 4 bit IOAPIC.
I tried with lifting local apic id to 0x80 or 0x40 above, and io apic
for 0 in linuxbios then load kernel 2.6.21 ( one year ago). it worked
well

YH
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/