A patch for the conflict of the irq vector "KDBENTER_VECTOR"

[Keith Owens]

On Thu, 21 Nov 2002 14:32:25 +0800, 
"Zhang, Sonic" <sonic.zhang at intel.com> wrote:
>--- linux/arch/i386/kernel/io_apic.c	Sun Nov 17 23:08:21 2002
>+++ linux-kdb/arch/i386/kernel/io_apic.c	Sun Nov 17 23:06:51 2002
>@@ -646,6 +646,11 @@
> 	if (current_vector == SYSCALL_VECTOR)
> 		goto next;
> 
>+#ifdef CONFIG_KDB
>+	if (current_vector == KDBENTER_VECTOR)
>+		goto next;
>+#endif
>+
> 	if (current_vector > FIRST_SYSTEM_VECTOR) {
> 		offset++;
> 		current_vector = FIRST_DEVICE_VECTOR + offset;
>
>	Do you think it's a reasonalble resolution?

That patch was added in kdb v2.4-2.4.19-i386-2.

2002-11-01 Keith Owens  <kaos at sgi.com>

       * Prevent SMP IRQ overwriting KDB_ENTER().
       * kdb v2.4-2.4.19-i386-2.

Index: 19.22/arch/i386/kernel/io_apic.c
--- 19.22/arch/i386/kernel/io_apic.c Fri, 01 Nov 2002 14:14:31 +1100 kaos (kdb-2.4-arch-i386/28_io_apic.c 1.1 644)
+++ 19.27/arch/i386/kernel/io_apic.c Fri, 01 Nov 2002 14:17:51 +1100 kaos (kdb-2.4-arch-i386/28_io_apic.c 1.2 644)
@@ -592,6 +595,10 @@ next:
 	current_vector += 8;
 	if (current_vector == SYSCALL_VECTOR)
 		goto next;
+#ifdef	CONFIG_KDB
+	if (current_vector == KDBENTER_VECTOR)
+		goto next;
+#endif	/* CONFIG_KDB */
 
 	if (current_vector > FIRST_SYSTEM_VECTOR) {
 		offset++;