linux-kernel - Re: [patch] clockevents: drivers for i386, fix #2

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061004105315.GA24940@elte.hu>
Date:	Wed, 4 Oct 2006 12:53:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...l.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>, Jim Gettys <jg@...top.org>,
	John Stultz <johnstul@...ibm.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [patch] clockevents: drivers for i386, fix #2


* Andrew Morton <akpm@...l.org> wrote:

> > hm, do you have the NMI watchdog enabled by any chance? [in 
> > particular, do you have nmi_watchdog=2?] Although your bootlog does 
> > not show it.
> > 
> 
> There's no nmi_watchdog setting in the kernel boot command line and 
> the NMI counter isn't incrementing.

there's one material difference we just found: in the !hres case we'll 
do the timer IRQ handling mostly from the lapic vector - while in 
mainline we do it from the irq0 vector. So, how does your 
/proc/interrupts look like? How frequently does LOC increase, and how 
frequently does IRQ 0 increase?

(meanwhile we'll fix and restore things so that it matches mainline 
behavior.)

	Ingo
-
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/