From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: dirk.brandewie@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dirk.brandweie@gmail.com, robert.a.kasten@intel.com,
charles.d.prestopine@intel.com, x86@kernel.org,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH 0/2] intel_pstate: Add support for hardware managed P states (HWP)
Date: Sat, 15 Nov 2014 00:54:14 +0100 [thread overview]
Message-ID: <1503544.Me07i8iiBH@vostro.rjw.lan> (raw)
In-Reply-To: <1415295647-4063-1-git-send-email-dirk.j.brandewie@intel.com>
On Thursday, November 06, 2014 09:40:45 AM dirk.brandewie@gmail.com wrote:
> From: Dirk Brandewie <dirk.j.brandewie@intel.com>
>
> This patch set adds support for HWP. When HWP is enabled the CPU will
> do P state autonomously and intel_pstate simply provides an interface
> to forward user preferences to the CPU while maintaining the
> interfaces required by the cpufreq core.
>
> Dirk Brandewie (2):
> x86: Add support for Intel HWP feature detection.
> intel_pstate: Add support for HWP
>
> Documentation/cpu-freq/intel-pstate.txt | 37 ++++++++----
> Documentation/kernel-parameters.txt | 3 +
> arch/x86/include/asm/cpufeature.h | 5 ++
> arch/x86/include/uapi/asm/msr-index.h | 41 +++++++++++++
> arch/x86/kernel/cpu/scattered.c | 5 ++
> drivers/cpufreq/intel_pstate.c | 102 +++++++++++++++++++++++++++++++-
> 6 files changed, 178 insertions(+), 15 deletions(-)
Both patches queued up for 3.19 (with assorted fixups), thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-11-14 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 17:40 dirk.brandewie
2014-11-06 17:40 ` [PATCH 1/2] x86: Add support for Intel HWP feature detection dirk.brandewie
2014-11-06 17:40 ` [PATCH 2/2] intel_pstate: Add support for HWP dirk.brandewie
2014-11-14 23:54 ` Rafael J. Wysocki [this message]
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=1503544.Me07i8iiBH@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=charles.d.prestopine@intel.com \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.brandweie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robert.a.kasten@intel.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®