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: <20080514090923.GC5607@alberich.amd.com>
Date:	Wed, 14 May 2008 11:09:23 +0200
From:	Andreas Herrmann <andreas.herrmann3@....com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Vegard Nossum <vegard.nossum@...il.com>, Andi Kleen <ak@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	S.Çağlar Onur <caglar@...dus.org.tr>,
	Valdis.Kletnieks@...edu, Matt Mackall <mpm@...enic.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] Lots of "rescheduling IPIs" in powertop

On Wed, May 14, 2008 at 08:56:05AM +0200, Ingo Molnar wrote:
> 
> * Vegard Nossum <vegard.nossum@...il.com> wrote:
> 
> > Hi,
> > 
> > Recap: powertop shows between 200-400 wakeups/second with the 
> > description "<kernel IPI>: Rescheduling interrupts" when all 
> > processors have load (e.g. I need to run two busy-loops on my 2-CPU 
> > system for this to show up).
> 
> ok, could you try the fix below? It was a mistake to make mwait use 
> dependent on power considerations - on a desktop CPU it is unlikely to 
> use more power than a simple HLT - and the IPIs are extra scheduling 
> latency and extra power used.

It depends on the CPU. For AMD CPUs that support MWAIT this is wrong.
Family 0x10 and 0x11 CPUs will enter C1 on HLT. Powersavings then
depend on a clock divisor and current Pstate of the core.

If all cores of a processor are in halt state (C1) the processor can
enter the C1E (C1 enhanced) state. If mwait is used this will never
happen.

Thus HLT saves more power than MWAIT here.

It might be best to switch off the mwait flag for these AMD CPU
families like it was introduced with commit
f039b754714a422959027cb18bb33760eb8153f0 (x86: Don't use MWAIT on AMD
Family 10)


Andreas


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ