From: Peter Zijlstra <peterz@infradead.org>
To: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
mike.turquette@linaro.org, morten.rasmussen@arm.com,
arjan@linux.intel.com, mingo@kernel.org, len.brown@intel.com,
rjw@rjwysocki.net, linaro-acpi@lists.linaro.org, arnd@arndb.de,
linux-acpi@vger.kernel.org, cpufreq@vger.kernel.org,
patches@linaro.org
Subject: Re: [RFC 0/3] Experimental patchset for CPPC
Date: Thu, 14 Aug 2014 22:51:43 +0200 [thread overview]
Message-ID: <20140814205143.GY6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1408046230-16439-1-git-send-email-ashwin.chaugule@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Thu, Aug 14, 2014 at 03:57:07PM -0400, Ashwin Chaugule wrote:
>
>
> What is CPPC:
> =============
>
> CPPC is the new interface for CPU performance control between the OS and the
> platform defined in ACPI 5.0+. The interface is built on an abstract
> representation of CPU performance rather than raw frequency. Basic operation
> consists of:
Why do we want this? Typically we've ignored ACPI and gone straight to
MSR access, intel_pstate and intel_idle were created especially to avoid
ACPI, so why return to it.
Also, the whole interface sounds like trainwreck (one would not expect
anything else from ACPI).
So _why_?
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-14 20:51 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 [this message]
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
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=20140814205143.GY6758@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=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