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]
Date:	Tue, 19 May 2015 15:25:53 +0800
From:	Huang Rui <ray.huang@....com>
To:	Borislav Petkov <bp@...en8.de>
CC:	Len Brown <lenb@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Aaron Lu <aaron.lu@...el.com>, "Li, Tony" <Tony.Li@....com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Mwait usage on AMD processors

On Thu, May 14, 2015 at 10:20:51PM +0800, Borislav Petkov wrote:
> On Thu, May 14, 2015 at 09:38:57PM +0800, Huang Rui wrote:
> > Is C1E here you mentioned is waiting state that use mwaitx enters at
> > AMD platform? If yes, please see below comments:
> > 
> > Current processor:
> > Power saving: C0 < C1E (AMD) < C1
> 
> How is C1 > C1E ?
> 
> C1E is the Enhanced C1.
> 

Apology that cause to misunderstand. It's not as same as intel.
Intel is able to go to C1E like you said, the C1E has less power
consumption than C1 on Intel platform.

But on AMD platform, mwaitx/mwait cannot go to C1 or C1E
like intel. The power consumption of waiting phase is somewhere in
between (C0 and C1). Actually, it's still in C0 but less power
consumption than normal C0.

> > Performance: Halt < Mwait <= Mwaitx
> 
> What performance? You're idle.
> 

The faster waiting exit speed. But it's hard to test the improvement,
do you have any idea? It's told by HW designer.

> > Halt -> C1, and Mwaitx/Mwait -> C1E (AMD)
> 
> Huh? Right now we do HLT on all AMD and the hw enters C1E after a bunch
> of stuff is fulfilled first. Are the plans to enter C1E from MWAIT now?
> 

Yes, I see all AMD platform only use HLT at current.

> > Consider about the balance between power consumption and performance,
> > so we want to expose the interface. And mwaitx has different opcode
> > with traditional mwait.
> 
> There's alternative()'s for that.
> 
> > Due to C1E (AMD) less power saving that real C1, so you can think it
> > still in C0 at current.
> 
> Which CPUs, current or upcoming?
> 

Current CPU, power consumption cannot go to deeper low power state
(C1) via mwaitx/mwait. But HW designers will implement it in future
processors.

Thanks,
Rui
--
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