From: Randy Dunlap <rdunlap@infradead.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Matthew Garrett <matthew.garrett@nebula.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>
Subject: Re: [PATCH 1/1] Introduce Intel RAPL cooling device driver
Date: Tue, 02 Apr 2013 14:42:39 -0700 [thread overview]
Message-ID: <515B50CF.7050103@infradead.org> (raw)
In-Reply-To: <1364940936-20846-2-git-send-email-jacob.jun.pan@linux.intel.com>
On 04/02/13 15:15, Jacob Pan wrote:
> RAPL(Running Average Power Limit) interface provides platform software
> with the ability to monitor, control, and get notifications on SOC
> power consumptions. Since its first appearance on Sandy Bridge, more
> features have being added to extend its usage. In RAPL, platforms are
> divided into domains for fine grained control. These domains include
> package, DRAM controller, CPU core (Power Plane 0), graphics uncore
> (power plane 1), etc.
>
> The purpose of this driver is to expose RAPL for userspace
> consumption. Overall, RAPL fits in the generic thermal layer in
> that platform level power capping and monitoring are mainly used for
> thermal management and thermal layer provides the abstracted interface
> needed to have portable applications.
>
> Specifically, userspace is presented with per domain cooling device
> with sysfs links to its kobject. Although RAPL domain provides many
> parameters for fine tuning, long term power limit is exposed as the
> single knob via cooling device state. Whereas the rest of the
> parameters are still accessible via the linked kobject. This simplifies
> the interface for both simple and advanced use cases.
>
> Eventfd is used to provide notifications to the userspace. At per domain
> level, use can choose any event capable parameters to register for
> threshold crossing notifications. This is shamelessly "borrowed" from
> cgroup with some trimming/fitting.
>
> Zhang, Rui's initial RAPL driver was used as a reference and starting
> point. Many thanks.
> https://lkml.org/lkml/2011/5/26/93
>
> Unlike the patch above, which is mainly for monitoring, this driver
> focus on the control and usability by user applications.
>
> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> ---
> drivers/platform/x86/Kconfig | 8 +
> drivers/platform/x86/Makefile | 1 +
> drivers/platform/x86/intel_rapl.c | 1323 +++++++++++++++++++++++++++++++++++++
> drivers/platform/x86/intel_rapl.h | 249 +++++++
> 4 files changed, 1581 insertions(+)
> create mode 100644 drivers/platform/x86/intel_rapl.c
> create mode 100644 drivers/platform/x86/intel_rapl.h
>
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index 3338437..34bcd52 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -781,4 +781,12 @@ config APPLE_GMUX
> graphics as well as the backlight. Currently only backlight
> control is supported by the driver.
>
> +config INTEL_RAPL
> + tristate "Intel RAPL Support"
> + depends on X86 && THERMAL
> + default y
> + ---help---
> + RAPL, AKA, Running Average Power Limit provides mechanisms to enforce
RAPL, aka Running Average Power Limit, provides mechanisms to enforce
or a.k.a., but not AKA
or even:
RAPL (Running Average Power Limit) provides mechanisms to enforce
> + and monitor per domain power consumption limits of supported Intel CPUs.
> +
> endif # X86_PLATFORM_DEVICES
--
~Randy
next prev parent reply other threads:[~2013-04-02 22:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 22:15 [PATCH 0/1] RAPL (Running Average Power Limit) driver Jacob Pan
2013-04-02 22:15 ` [PATCH 1/1] Introduce Intel RAPL cooling device driver Jacob Pan
2013-04-02 21:42 ` Randy Dunlap [this message]
2013-04-02 21:47 ` Randy Dunlap
2013-04-02 23:04 ` Greg Kroah-Hartman
2013-04-02 22:35 ` Joe Perches
2013-04-02 23:00 ` Greg KH
2013-04-02 23:03 ` Greg KH
2013-04-02 23:33 ` Jacob Pan
2013-04-02 23:48 ` Greg KH
2013-04-03 0:17 ` Jacob Pan
2013-04-03 16:30 ` Greg KH
2013-04-03 18:03 ` Jacob Pan
2013-04-05 20:24 ` Greg KH
2013-04-02 23:53 ` Jacob Pan
2013-04-03 0:13 ` Greg KH
2013-04-03 4:48 ` Jacob Pan
2013-04-03 16:35 ` Greg KH
2013-04-03 17:35 ` Jacob Pan
2013-04-05 20:23 ` Greg KH
2013-04-05 21:33 ` Jacob Pan
2013-04-05 21:46 ` Greg KH
2013-04-03 10:24 ` Paul Bolle
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=515B50CF.7050103@infradead.org \
--to=rdunlap@infradead.org \
--cc=arjan@linux.intel.com \
--cc=jacob.jun.pan@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.