Skip to contentSkip to conversation

x86: UV BAU interrupt vector duplicated

PATCH In review Cliff Wickman 1 participant 2 messages Dec 11, 2009 – Dec 13, 2009 x86

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 x86: UV BAU interrupt vector duplicated

From: Cliff Wickman <[email protected]>

Diffed against 2.6.32

Interrupt vector 0xec has been doubly defined in irq_vectors.h

It seems arbitrary whether LOCAL_PENDING_VECTOR or UV_BAU_MESSAGE is the higher number. As long as they are unique.
If they are not unique we'll hit a BUG in alloc_system_vector().

---
 arch/x86/include/asm/irq_vectors.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/include/asm/irq_vectors.h +1 -1
Index: linux/arch/x86/include/asm/irq_vectors.h
===================================================================
@@ -120,7 +120,7 @@
  */
 #define LOCAL_PENDING_VECTOR		0xec
 
-#define UV_BAU_MESSAGE			0xec
+#define UV_BAU_MESSAGE			0xea
 
 /*
  * Self IPI vector for machine checks
#1 lore raw

[tip:x86/urgent] x86: Fix duplicated UV BAU interrupt vector

Commit-ID:  1d865fb728bd6bbcdfbd6ec1e2b8ade3b4805641
Gitweb:     http://git.kernel.org/tip/1d865fb728bd6bbcdfbd6ec1e2b8ade3b4805641
Author:     Cliff Wickman <[email protected]>
AuthorDate: Fri, 11 Dec 2009 11:36:18 -0600
Committer:  Ingo Molnar <[email protected]>
CommitDate: Sun, 13 Dec 2009 08:17:40 +0100

x86: Fix duplicated UV BAU interrupt vector

Interrupt vector 0xec has been doubly defined in irq_vectors.h

It seems arbitrary whether LOCAL_PENDING_VECTOR or UV_BAU_MESSAGE is the higher number. As long as they are unique. If they are not unique we'll hit a BUG in alloc_system_vector().

LKML-Reference: <[email protected]>

---
 arch/x86/include/asm/irq_vectors.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/x86/include/asm/irq_vectors.h +1 -1
index 6a635bd..4611f08 100644
@@ -113,7 +113,7 @@
  */
 #define LOCAL_PENDING_VECTOR		0xec
 
-#define UV_BAU_MESSAGE			0xec
+#define UV_BAU_MESSAGE			0xea
 
 /*
  * Self IPI vector for machine checks