linux-kernel - why would irq0 have many many more interrupts than LOC?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4FA197DD.8030702@genband.com>
Date:	Wed, 02 May 2012 14:23:57 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	linux-kernel@...r.kernel.org
Subject: why would irq0 have many many more interrupts than LOC?

I have an x86_64 2.6.27 kernel running on a Sandy Bridge machine.

/proc/interrupts currently shows 75573114 counts for irq0 on cpu 0 and 
no counts on other cpus and between 2973587 and 4185923 counts for "LOC" 
spread across all cpus including cpu0.

The following are enabled.

CONFIG_GENERIC_HARDIRQS=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000

It almost seems like it's taking a timer interrupt on cpu0 for every 
local timer interrupt on every cpu.  Surely that's not design intent?

Any ideas on how to fix this?

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/