From: Andi Kleen <andi@firstfloor.org>
To: Joe Korty <joe.korty@ccur.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
"H. Peter Anvin" <hpa@zytor.com>,
mingo@elte.hu, tglx@linutronix.de,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
jason.baietto@ccur.com
Subject: Re: [PATCH] expand /proc/interrupts to include missing vectors, v3
Date: 31 Jul 2007 19:02:01 +0200 [thread overview]
Message-ID: <p73wswgpkvq.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070731141941.GA3112@tsunami.ccur.com>
Joe Korty <joe.korty@ccur.com> writes:
> spurious interrupts
>
> A threshold interrupt occurs when ECC memory correction
> is occuring at too high a frequency.
It's configurable and the default is off. Also
it's only on AMD hardware.
Your description is a little misleading.
> Thresholds are used
> by the ECC hardware as occasional ECC failures are part
> of normal operation,
Not really.
> ===================================================================
> --- 2.6.23-rc1-git7.orig/arch/i386/kernel/apic.c 2007-07-30 19:08:05.000000000 -0400
> +++ 2.6.23-rc1-git7/arch/i386/kernel/apic.c 2007-07-30 19:08:07.000000000 -0400
> @@ -1280,6 +1280,7 @@
> printk(KERN_INFO "spurious APIC interrupt on CPU#%d, "
> "should never happen.\n", smp_processor_id());
> irq_exit();
> + __get_cpu_var(irq_stat).irq_spur_counts++;
Wouldn't it be safer on preemptible kernels to have that inside
the irq_exit?
> }
>
> /*
> Index: 2.6.23-rc1-git7/arch/i386/kernel/cpu/mcheck/p4.c
> ===================================================================
> --- 2.6.23-rc1-git7.orig/arch/i386/kernel/cpu/mcheck/p4.c 2007-07-30 19:08:05.000000000 -0400
> +++ 2.6.23-rc1-git7/arch/i386/kernel/cpu/mcheck/p4.c 2007-07-30 19:08:07.000000000 -0400
> @@ -62,6 +62,7 @@
> irq_enter();
> vendor_thermal_interrupt(regs);
> irq_exit();
> + __get_cpu_var(irq_stat).irq_thermal_counts++;
> }
>
> /* P4/Xeon Thermal regulation detect and init */
> Index: 2.6.23-rc1-git7/arch/i386/kernel/irq.c
> ===================================================================
> --- 2.6.23-rc1-git7.orig/arch/i386/kernel/irq.c 2007-07-30 19:08:05.000000000 -0400
> +++ 2.6.23-rc1-git7/arch/i386/kernel/irq.c 2007-07-31 09:40:58.000000000 -0400
> @@ -284,14 +284,41 @@
> seq_printf(p, "NMI: ");
> for_each_online_cpu(j)
> seq_printf(p, "%10u ", nmi_count(j));
> - seq_putc(p, '\n');
> + seq_printf(p, " Non-maskable interrupts\n");
> #ifdef CONFIG_X86_LOCAL_APIC
> seq_printf(p, "LOC: ");
> for_each_online_cpu(j)
> seq_printf(p, "%10u ",
> per_cpu(irq_stat,j).apic_timer_irqs);
> - seq_putc(p, '\n');
> + seq_printf(p, " Local interrupts\n");
> #endif
> +#ifdef CONFIG_SMP
> + seq_printf(p, "RES: ");
I think it would be better to use 5-6 char identifiers even
when it whacks the columns a bit; otherwise
nobody will know what it means. e.g. SCHED here.
Also there you should update proc(5) and send a patch
to the manpage maintainer.
> Index: 2.6.23-rc1-git7/arch/x86_64/kernel/apic.c
> ===================================================================
> --- 2.6.23-rc1-git7.orig/arch/x86_64/kernel/apic.c 2007-07-30 19:08:05.000000000 -0400
> +++ 2.6.23-rc1-git7/arch/x86_64/kernel/apic.c 2007-07-30 19:08:07.000000000 -0400
> @@ -1118,6 +1118,7 @@
> asmlinkage void smp_spurious_interrupt(void)
> {
> unsigned int v;
> +
Don't add white space.
-Andi
next prev parent reply other threads:[~2007-07-31 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:05 [PATCH] create /proc/all-interrupts Joe Korty
2007-07-26 18:56 ` H. Peter Anvin
2007-07-30 17:33 ` Sven-Thorsten Dietrich
2007-07-30 19:32 ` Andrew Morton
2007-07-30 19:42 ` Joe Korty
2007-07-31 0:17 ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Joe Korty
2007-07-31 0:48 ` Gabriel C
2007-07-31 1:48 ` Andrew Morton
2007-07-31 14:19 ` [PATCH] expand /proc/interrupts to include missing vectors, v3 Joe Korty
2007-07-31 17:02 ` Andi Kleen [this message]
2007-07-31 20:29 ` Joe Korty
2007-07-31 21:06 ` [PATCH] expand /proc/interrupts to include missing vectors, v4 Joe Korty
2007-08-01 13:29 ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Lennart Sorensen
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=p73wswgpkvq.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jason.baietto@ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox