summaryrefslogtreecommitdiff
path: root/include/asm-x86/apic.h
diff options
context:
space:
mode:
authorSuresh Siddha <suresh.b.siddha@intel.com>2008-07-22 14:13:11 (GMT)
committerIngo Molnar <mingo@elte.hu>2008-07-22 15:29:22 (GMT)
commitdf1be4372eae5f104b7fb4991bc4b35f00b11a11 (patch)
tree8d812a128eaed7c27fdb3a7913b050e35e3d6145 /include/asm-x86/apic.h
parent1b9b89e7f163336ad84200b66a17284dbf26aced (diff)
downloadlinux-fsl-qoriq-df1be4372eae5f104b7fb4991bc4b35f00b11a11.tar.xz
x64, apic: use generic apic_write() for ack_APIC_irq()
I tested tip/master and found an issue (patch attached) for x2apic support. This is not because of the recent merges we had, but because of something(where we still access memory based interface after enabling x2apic mode) that slipped through my earlier tests. Probably it is a good idea to unmap the memory mapped interface, once we switch to x2apic mode. That will catch the issues much earlier. I will post another patch for this. ack_APIC_irq() is used at too many generic places (and not just during irq_chip handling!) to use the native_apic_mem_write(). For ex, this will break x2apic based systems. Fix ack_APIC_irq() to use the generic apic_write() even for 64-bit. Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com> Cc: suresh.b.siddha@intel.com Cc: yong.y.wang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'include/asm-x86/apic.h')
-rw-r--r--include/asm-x86/apic.h4
1 files changed, 0 insertions, 4 deletions
diff --git a/include/asm-x86/apic.h b/include/asm-x86/apic.h
index 5133991..502ca65 100644
--- a/include/asm-x86/apic.h
+++ b/include/asm-x86/apic.h
@@ -136,11 +136,7 @@ static inline void ack_APIC_irq(void)
*/
/* Docs say use 0 for future compatibility */
-#ifdef CONFIG_X86_32
apic_write(APIC_EOI, 0);
-#else
- native_apic_mem_write(APIC_EOI, 0);
-#endif
}
extern int lapic_get_maxlvt(void);