linux-kernel - Re: 2.6.19-rc4-mm1: noidlehz problems

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

Date:	Wed, 01 Nov 2006 21:55:01 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>, mingo@...hat.com,
	Andrew Morton <akpm@...l.org>
Subject: Re: 2.6.19-rc4-mm1: noidlehz problems

On Wed, 2006-11-01 at 15:22 +0000, Matthew Garrett wrote:
> On Wed, Nov 01, 2006 at 02:02:57PM +0100, Arjan van de Ven wrote:
> 
> > In some (hardware) C-states, the local apic timer stops (as does the
> > TSC), while in others it keeps running. If you change from AC to
> > battery, the bios can change the meaning of a software C-state from one
> > where local apic timer keeps going to one where it stops. This obviously
> > upsets the hrtimers/tickless code since that uses local apic timer for
> > event generation....
> 
> Is there any hope of working around this? I'd have expected that the 
> most useful case for the tickless code was also the case where we want 
> to be using C3/C4...

Can you try the following patches please ?

http://tglx.de/projects/hrtimers/2.6.19-rc4-mm1/patch-2.6.19-rc4-mm1-hrt-dyntick1.patch

This addresses the C34/C4 issue

	tglx

	

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