> John,
>
> That looks reasonable to me. The one possible catch would be for systems so
> old they don't do SMI -- 386s and 486s, I imagine. If this code doesn't barf
> on them when CONFIG_IO_APIC is turned on, then it should be fine (minus the
> printk).
>
> (I believe there was at least one such system, the Intel Xpress box. It
> contained a 486 and seperate APIC chips.)
Referring to this?
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: INTEL Product ID: XXPRESS APIC at: 0xFEE00000
Processor #0 5:2 APIC version 16
Processor #3 5:2 APIC version 16
Processor #4 5:2 APIC version 16
Unknown bustype XPRESS - ignoring
I/O APIC #14 Version 17 at 0xFEC00000.
I/O APIC #13 Version 17 at 0xFFE7F800.
Enabling APIC mode: Flat. Using 2 I/O APICs
Processors: 3
John's check should be safe as it doesn't touch hardware anyway.
Zwane
-- function.linuxpower.ca - 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/