Sure, I can verify it. The I/O APICs in shipped summit chipsets contains a
version ID of 0x11 instead of 0x14 to 0x1F. The high performance folks
claimed that Intel specified 0x14 for the local APICs, but left their orange
jacket docs saying 0x1X for I/O APICs until after the chips taped out.
Whatever. In any case, there are boxes in the field that contain those
version numbers. We can recognize them using the OEM and product strings in
the MPS and ACPI tables, so it's only an annoyance.
> > Okay, this was wrong before, but any chance you could use proper
> > style here (i.e. if ()
> > Again.
>
> oops.. I somehow missed these 'if' coding style stuff. changing it
> immediately.
>
> > > + define_bool CONFIG_X86_CLUSTERED_APIC y
> >
> > Do we really need CONFIG_X86_APIC_CLUSTER _and_
> > CONFIG_X86_CLUSTERED_APIC?
>
> I will also eliminate CONFIG_X86_APIC_CLUSTER and use
> CONFIG_X86_CLUSTERED_APIC directly.
>
> > - if (clustered_apic_mode == CLUSTERED_APIC_NUMAQ) {
> > + if (clustered_apic_mode &&
> > + (configured_platform_type ==
> > CONFIGURED_PLATFORM_NUMA) ) {
> >
> > Doesn;t configured_platform_type == CONFIGURED_PLATFORM_NUMA imply
> > clustered_apic_mode? and it should be at least
> > CONFIGURED_PLATFORM_NUMAQ,
> > btw. Probably better something short like SUBARCH_NUMAQ..
>
> Yes, right now CONFIGURED_PLATFORM_NUMA implies clustered_apic_mode, and
> one of the checks in the above 'if' is redundant. Will do a search and
> replace of NUMA by NUMAQ.
>
>
> Thanks,
> Venkatesh
-- James Cleverdon IBM xSeries Linux Solutions {jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com- 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/