public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mike Turquette <mike.turquette@linaro.org>,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	mingo@kernel.org, len.brown@intel.com, rjw@rjwysocki.net,
	"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-acpi@vger.kernel.org, cpufreq@vger.kernel.org,
	Patch Tracking <patches@linaro.org>,
	Dirk Brandewie <dirk.brandewie@gmail.com>
Subject: Re: [RFC 0/3] Experimental patchset for CPPC
Date: Fri, 15 Aug 2014 16:00:06 +0200	[thread overview]
Message-ID: <20140815140006.GH19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <53EE0E5B.3050004@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On Fri, Aug 15, 2014 at 06:42:51AM -0700, Arjan van de Ven wrote:
> 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.

OK, so we should just forget about 'power aware scheduling' for Intel?

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-08-15 14:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 19:57 [RFC 0/3] Experimental patchset for CPPC Ashwin Chaugule
2014-08-14 19:57 ` [RFC 1/3] ACPI: Add support for Platform Communication Channel Ashwin Chaugule
2014-08-14 20:11   ` Ashwin Chaugule
2014-08-14 19:57 ` [RFC 2/3] CPPC: Add support for Collaborative Processor Performance Control Ashwin Chaugule
2014-08-14 20:12   ` Ashwin Chaugule
2014-08-14 19:57 ` [RFC 3/3] CPPC: Add ACPI accessors to CPC registers Ashwin Chaugule
2014-08-14 20:12   ` Ashwin Chaugule
2014-08-14 20:11 ` [RFC 0/3] Experimental patchset for CPPC Ashwin Chaugule
2014-08-14 20:51 ` Peter Zijlstra
2014-08-14 21:56   ` Ashwin Chaugule
2014-08-15  6:19     ` Peter Zijlstra
2014-08-15 13:08       ` Ashwin Chaugule
2014-08-15 13:42         ` Arjan van de Ven
2014-08-15 13:53           ` Arjan van de Ven
2014-08-15 14:24             ` Ashwin Chaugule
2014-08-15 15:47               ` Arjan van de Ven
2014-08-15 16:41                 ` Ashwin Chaugule
2014-08-15 22:11                   ` Len Brown
2014-08-18 15:04                     ` Ashwin Chaugule
2014-08-15 14:00           ` Peter Zijlstra [this message]
2014-08-15 14:07         ` Peter Zijlstra
2014-08-15 14:37           ` Ashwin Chaugule
2014-08-15 14:41             ` Peter Zijlstra
2014-08-18 14:54               ` Ashwin Chaugule
2014-08-15 22:22 ` Len Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140815140006.GH19379@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=arjan@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=ashwin.chaugule@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.turquette@linaro.org \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=patches@linaro.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox