From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755609AbbESH1C (ORCPT ); Tue, 19 May 2015 03:27:02 -0400 Received: from mail-bn1bon0140.outbound.protection.outlook.com ([157.56.111.140]:52936 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754042AbbESHYu (ORCPT ); Tue, 19 May 2015 03:24:50 -0400 Authentication-Results: spf=none (sender IP is 165.204.84.222) smtp.mailfrom=amd.com; alien8.de; dkim=none (message not signed) header.d=none; X-WSS-ID: 0NOL5X6-08-G79-02 X-M-MSG: Date: Tue, 19 May 2015 15:25:53 +0800 From: Huang Rui To: Borislav Petkov CC: Len Brown , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" , Fengguang Wu , Aaron Lu , "Li, Tony" , Thomas Gleixner Subject: Re: Mwait usage on AMD processors Message-ID: <20150519072552.GA28547@hr-slim.amd.com> References: <20150514065451.GA29830@hr-slim.amd.com> <20150514092137.GA29235@pd.tnic> <20150514101727.GA6552@hr-slim.amd.com> <20150514112303.GC29125@pd.tnic> <20150514133857.GB6552@hr-slim.amd.com> <20150514142051.GD29125@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20150514142051.GD29125@pd.tnic> User-Agent: Mutt/1.5.21 (2010-09-15) X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1;BN1AFFO11FD017;1:/DzcKwtnoTLa8i23BQkHjVhQXfc8G9DBdZnWuecFB/fglN1UV0FIPPsq05j7QolezZ+hPJ84VslQVIHtI5vkhd0JkAN2NyuDzYEhSPw0rU0vLO1HJGQucqlCeSHcupplNbL1mjt1mh3HIBC+Bc6f8qHG3gY60/XuFle/G6X3NLDACATweOvwav2G34uYdVw7jyABxp4I0tmVbjGaSvXuitErAe5yQvKq/WQRZ0539xTpcrj6j9QZlbqV2NlFArb1fVQDJJ4cD/AmQR+eE6tHw0BqEbD4Y4ImmhXkRoEkJR0= X-Forefront-Antispam-Report: CIP:165.204.84.222;CTRY:US;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10019020)(6009001)(428002)(189002)(199003)(51704005)(24454002)(164054003)(23726002)(110136002)(5001860100001)(5001830100001)(189998001)(2950100001)(46406003)(62966003)(106466001)(33656002)(83506001)(50986999)(54356999)(47776003)(101416001)(50466002)(64706001)(97756001)(86362001)(87936001)(4001540100001)(97736004)(77156002)(77096005)(68736005)(76176999)(4001350100001)(92566002)(46102003)(105586002)(93886004)(53416004);DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR02MB068;H:atltwp02.amd.com;FPR:;SPF:None;PTR:InfoDomainNonexistent;MX:1;A:1;LANG:en; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR02MB068; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:BLUPR02MB068;BCL:0;PCL:0;RULEID:;SRVR:BLUPR02MB068; X-Forefront-PRVS: 0581B5AB35 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 May 2015 07:24:47.1761 (UTC) X-MS-Exchange-CrossTenant-Id: fde4dada-be84-483f-92cc-e026cbee8e96 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=fde4dada-be84-483f-92cc-e026cbee8e96;Ip=[165.204.84.222];Helo=[atltwp02.amd.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR02MB068 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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