> Not sure if we ever support CPUs with different APIC versions. That will > probably require some ACPI SPEC changes too.. > > I would say, for now just follow the i386 code. Ok I applied the patch. Thanks. -Andi - 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/
- References:
- Re: APIC version and 8-bit APIC IDs
- From: Andi Kleen <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Martin Wilck <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Andi Kleen <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Martin Wilck <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Martin Wilck <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Andi Kleen <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: "Siddha, Suresh B" <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: Andi Kleen <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- From: "Siddha, Suresh B" <[email protected]>
- Re: APIC version and 8-bit APIC IDs
- Prev by Date: [patch 38/39] [RFC] remap_file_pages protection support: avoid dirtying on read faults for NONUNIFORM pages
- Next by Date: [patch 22/39] remap file pages protection support: use FAULT_SIGSEGV for protection checking, uml bits
- Previous by thread: Re: APIC version and 8-bit APIC IDs
- Next by thread: Re: APIC version and 8-bit APIC IDs
- Index(es):
