linux-kernel - Re: [PATCH v5 2/2] x86, mwaitt: introduce mwaix delay with a configurable timer

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:	Mon, 15 Jun 2015 22:33:08 +0800
From:	Huang Rui <ray.huang@....com>
To:	Borislav Petkov <bp@...e.de>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Andy Lutomirski <luto@...capital.net>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Len Brown <lenb@...nel.org>,
	John Stultz <john.stultz@...aro.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	<linux-kernel@...r.kernel.org>, <x86@...nel.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Aaron Lu <aaron.lu@...el.com>,
	Suravee Suthikulanit <suravee.suthikulpanit@....com>,
	Tony Li <tony.li@....com>, Ken Xue <ken.xue@....com>
Subject: Re: [PATCH v5 2/2] x86, mwaitt: introduce mwaix delay with a
 configurable timer

On Mon, Jun 15, 2015 at 04:25:59PM +0200, Borislav Petkov wrote:
> On Mon, Jun 15, 2015 at 10:04:19PM +0800, Huang Rui wrote:
> > Hmm, the current processor cannot enter C1 with MWAITX, so I don't
> > confirm if it would have higher wakeup latency on C1 in future.
> 
> I remember you saying MWAITX enters currently something between C1 and
> C0. How does that behave wrt latency and power savings?
> 

Yes, right. The power consumption is less than C0 (C0 > MWAITX > C1).
The waiting exit speed is faster than HTL.

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/