From: ethan zhao <ethan.zhao@oracle.com>
To: Ethan Zhao <ethan.zhao@oracle.com>
Cc: dirk.j.brandewie@intel.com, viresh.kumar@linaro.org,
rjw@rjwysocki.net, corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
ethan.kernel@gmail.com, joe.jin@oracle.com,
brian.maly@oracle.com
Subject: Re: [PATCH] intel_pstate: allow to be built as module and handle Sun server power capping.
Date: Tue, 18 Nov 2014 16:32:18 +0800 [thread overview]
Message-ID: <546B0412.8060102@oracle.com> (raw)
In-Reply-To: <1416299253-14912-1-git-send-email-ethan.zhao@oracle.com>
Sorry, I missed the -n to git format-patch,
please ignore this patch.
Thanks,
Ethan
On 2014/11/18 16:27, Ethan Zhao wrote:
> Oracle Sun servers(X86) have power capping features that work via ACPI _PPC method,
> patch No.1 is used to skip this driver if Oracle Sun server and _PPC detected. patch
> No.2 is used to allow the driver to be configured and built as a module, so provide
> the flexibility of configuration by userland. patch No.3 introduce a module parameter
> and a kernel command line parameter, let user could force it loaded even on Oracle Sun
> Servers(X86), that will be useful for debug\test\workaround etc purpose.
>
> These patches have been tested on Oracle Sun server X4-2 series with following
> cases on stable v3.18-rc3.
>
> a. Configure and build intel_pstate as builtin.
> Boot without any kernel line parameter.
> Boot with intel_pstate=ignore_acpi_ppc.
> b. Configure and build intel_pstate as module.
> Load intel_pstate drive without any module parameter.
> Load intel_pstate driver with ignore_acpi_ppc=1
>
> These cases passed and work fine.
> --
> Brian Maly (1):
> intel_pstate: allow driver to be built as a module
>
> Ethan Zhao (2):
> intel_pstate: skip the driver if Sun server has ACPI _PPC method
> intel_pstate: add module and kernel command line parameter to ignore
> ACPI _PPC
>
> Documentation/kernel-parameters.txt | 3 +++
> drivers/cpufreq/Kconfig.x86 | 2 +-
> drivers/cpufreq/intel_pstate.c | 32 ++++++++++++++++++++++++++++++++
> 3 files changed, 36 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2014-11-18 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 8:27 [PATCH] intel_pstate: allow to be built as module and handle Sun server power capping Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: skip the driver if Sun server has ACPI _PPC method Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: allow driver to be built as a module Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: add module and kernel command line parameter to ignore ACPI _PPC Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: allow to be built as module and handle Sun server power capping Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: skip the driver if Sun server has ACPI _PPC method Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: allow driver to be built as a module Ethan Zhao
2014-11-18 8:27 ` [PATCH] intel_pstate: add module and kernel command line parameter to ignore ACPI _PPC Ethan Zhao
2014-11-18 8:32 ` ethan zhao [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=546B0412.8060102@oracle.com \
--to=ethan.zhao@oracle.com \
--cc=brian.maly@oracle.com \
--cc=corbet@lwn.net \
--cc=dirk.j.brandewie@intel.com \
--cc=ethan.kernel@gmail.com \
--cc=joe.jin@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).