[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1416299826-15813-5-git-send-email-ethan.zhao@oracle.com>
Date: Tue, 18 Nov 2014 17:37:03 +0900
From: Ethan Zhao <ethan.zhao@...cle.com>
To: dirk.j.brandewie@...el.com, viresh.kumar@...aro.org,
rjw@...ysocki.net, corbet@....net
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, ethan.kernel@...il.com,
joe.jin@...cle.com, brian.maly@...cle.com,
Ethan Zhao <ethan.zhao@...cle.com>
Subject: [PATCH 0/3] intel_pstate: allow to be built as module and handle Sun server power capping.
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(-)
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists