From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751576AbaHONnR (ORCPT ); Fri, 15 Aug 2014 09:43:17 -0400 Received: from mga09.intel.com ([134.134.136.24]:25199 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751536AbaHONnN (ORCPT ); Fri, 15 Aug 2014 09:43:13 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,870,1400050800"; d="scan'208";a="559019421" Message-ID: <53EE0E5B.3050004@linux.intel.com> Date: Fri, 15 Aug 2014 06:42:51 -0700 From: Arjan van de Ven User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ashwin Chaugule , Peter Zijlstra CC: lkml , Catalin Marinas , Mike Turquette , Morten Rasmussen , mingo@kernel.org, len.brown@intel.com, rjw@rjwysocki.net, "linaro-acpi@lists.linaro.org" , Arnd Bergmann , linux-acpi@vger.kernel.org, cpufreq@vger.kernel.org, Patch Tracking , Dirk Brandewie Subject: Re: [RFC 0/3] Experimental patchset for CPPC References: <1408046230-16439-1-git-send-email-ashwin.chaugule@linaro.org> <20140814205143.GY6758@twins.programming.kicks-ass.net> <20140815061917.GX19379@twins.programming.kicks-ass.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/15/2014 6:08 AM, Ashwin Chaugule wrote: > (b) we come up with ways to provide the bounds around a Desired value > using the information from the platform. (long term) > > I briefly looked at the x86 HWP (Hardware Performance States) in the > s/w manual again. Its essentially an implementation of CPPC. It seems > like X86 has implemented most if not all these registers as MSRs. I'm > really interested in knowing if anyone there is/has been working on > using them and what they found. we've found that so far that there are two reasonable options 1) Let the OS device (old style) 2) Let the hardware decide (new style) 2) is there in practice today in the turbo range (which is increasingly the whole thing) and the hardware can make decisions about power budgetting on a timescale the OS can never even dream of, so once you give control the the hardware (with CPPC or native) it's normally better to just get out of the way as OS.