From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: warn on apic error
Date: Fri, 18 Jul 2008 21:44:13 +0400 [thread overview]
Message-ID: <20080718174413.GD6897@asus> (raw)
In-Reply-To: <20080718172821.GA4149@localhost.localdomain>
[Vegard Nossum - Fri, Jul 18, 2008 at 07:28:21PM +0200]
| From e89f2a9f33d01a2df7553b63cb1df525c6e75ad4 Mon Sep 17 00:00:00 2001
| From: Vegard Nossum <vegard.nossum@gmail.com>
| Date: Fri, 18 Jul 2008 19:14:06 +0200
| Subject: [PATCH] x86: warn on apic error
|
| There are certain APIC errors which are obviously programmer errors,
| e.g. writing to illegal APIC registers, or sending invalid interrupt
| vectors. Since the error interrupt happens spot on the erroneous code,
| we might as well make a bit of noise about it and display the stack-
| trace.
|
| Cc: Maciej W. Rozycki <macro@linux-mips.org>
| Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
| ---
| arch/x86/kernel/apic_32.c | 1 +
| arch/x86/kernel/apic_64.c | 1 +
| 2 files changed, 2 insertions(+), 0 deletions(-)
|
| diff --git a/arch/x86/kernel/apic_32.c b/arch/x86/kernel/apic_32.c
| index a437d02..b9289cb 100644
| --- a/arch/x86/kernel/apic_32.c
| +++ b/arch/x86/kernel/apic_32.c
| @@ -1317,6 +1317,7 @@ void smp_error_interrupt(struct pt_regs *regs)
| */
| printk(KERN_DEBUG "APIC error on CPU%d: %02lx(%02lx)\n",
| smp_processor_id(), v , v1);
| + WARN_ON(v1 & ((1 << 0) | (1 << 2) | (1 << 5) | (1 << 7)));
| irq_exit();
| }
|
| diff --git a/arch/x86/kernel/apic_64.c b/arch/x86/kernel/apic_64.c
| index 1e3d32e..2d959f2 100644
| --- a/arch/x86/kernel/apic_64.c
| +++ b/arch/x86/kernel/apic_64.c
| @@ -997,6 +997,7 @@ asmlinkage void smp_error_interrupt(void)
| */
| printk(KERN_DEBUG "APIC error on CPU%d: %02x(%02x)\n",
| smp_processor_id(), v , v1);
| + WARN_ON(v1 & ((1 << 0) | (1 << 2) | (1 << 5) | (1 << 7)));
| irq_exit();
| }
|
| --
| 1.5.5.1
|
|
Hi Vegard, i think you better should use #APIC_ESR_... macroses
from apicdef.h instead of hardcoded bits.
- Cyrill -
next prev parent reply other threads:[~2008-07-18 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 17:28 [PATCH] x86: warn on apic error Vegard Nossum
2008-07-18 17:44 ` Cyrill Gorcunov [this message]
2008-07-18 17:45 ` Vegard Nossum
2008-07-18 17:49 ` Cyrill Gorcunov
2008-07-18 19:09 ` Maciej W. Rozycki
2008-07-18 19:13 ` Cyrill Gorcunov
2008-07-19 12:59 ` Cyrill Gorcunov
2008-07-19 23:08 ` Maciej W. Rozycki
2008-07-20 6:38 ` Cyrill Gorcunov
2008-07-18 19:02 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080718174413.GD6897@asus \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.