From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Matthew Garrett <matthew.garrett@nebula.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>, Zhang Rui <rui.zhang@intel.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH v4 0/1] RAPL (Running Average Power Limit) driver
Date: Tue, 9 Apr 2013 16:46:48 -0700 [thread overview]
Message-ID: <1365551209-14392-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)
Changes since V3:
- Removed dependency on platform_device/platform_driver.
I initially used platform bus for the purpose of linking
RAPL domain device objects to thermal sysfs. For this simplified
version we don't need this anymore nor do we need any
resources/platform data. This simplified version only needs
MSR access. (not to avoid .release() :). I should be freeing
device data after it gets called from driver core)
- merged header file into .c file, there is no public data nor
APIs.
- misc. cleanups based on reviews
Changes since V2:
This is a simpler version which only exposes interface via
the generic thermal layer. No new ABI introduced.
RAPL driver does some automatic settings to the related power
parameters based on user's single input from thermal cooling
device interface.
On the other side, more work needed to fully use RAPL
interface. This is likely result in adding more knobs in the
generic thermal sysfs.
- deleted event notifications
- deleted per domain device and RAPL class and their private
sysfs
- added more logic to do some automatic settings based on
user input. e.g. will enable clamping by default and set
a reasonable time window for long term power limits.
Changes since V1:
- use 'struct device' instead of raw kobject to represent
RAPL domains
- changed eventfd control interface to use event string
instead of passing file descriptors that cannot be
authenticated in sysfs directory
- clean ups based on v1 reviews
- use kcalloc for arrays
- drop dependencies on X86
- misc cleanups
Jacob Pan (1):
Introduce Intel RAPL cooling device driver
drivers/platform/x86/Kconfig | 9 +
drivers/platform/x86/Makefile | 1 +
drivers/platform/x86/intel_rapl.c | 889 +++++++++++++++++++++++++++++++++++++
3 files changed, 899 insertions(+)
create mode 100644 drivers/platform/x86/intel_rapl.c
--
1.7.9.5
next reply other threads:[~2013-04-09 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 23:46 Jacob Pan [this message]
2013-04-09 23:46 ` [PATCH v4 1/1] Introduce Intel RAPL cooling device driver Jacob Pan
2013-04-09 23:52 ` Greg Kroah-Hartman
2013-04-10 0:01 ` Joe Perches
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=1365551209-14392-1-git-send-email-jacob.jun.pan@linux.intel.com \
--to=jacob.jun.pan@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
/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