2013-10-12 07:54:56 +08:00
|
|
|
#
|
|
|
|
|
# Generic power capping sysfs interface configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menuconfig POWERCAP
|
|
|
|
|
bool "Generic powercap sysfs driver"
|
|
|
|
|
help
|
|
|
|
|
The power capping sysfs interface allows kernel subsystems to expose power
|
|
|
|
|
capping settings to user space in a consistent way. Usually, it consists
|
|
|
|
|
of multiple control types that determine which settings may be exposed and
|
|
|
|
|
power zones representing parts of the system that can be subject to power
|
|
|
|
|
capping.
|
|
|
|
|
|
|
|
|
|
If you want this code to be compiled in, say Y here.
|
|
|
|
|
|
|
|
|
|
if POWERCAP
|
|
|
|
|
# Client driver configurations go here.
|
PowerCap: Introduce Intel RAPL power capping driver
The Intel Running Average Power Limit (RAPL) technology provides platform
software with the ability to monitor, control, and get notifications on
power usage.
This feature is present in all Sandy Bridge and later Intel processors.
Newer models allow more fine grained controls to be applied. In RAPL,
power control is divided into domains, which include package, DRAM
controller, CPU core (Power Plane 0), graphics uncore (power plane 1), etc.
The purpose of this driver is to expose the RAPL settings to userspace.
Overall, RAPL fits in the new powercap class driver in that platform
level power capping controls are exposed via this generic interface.
This driver is based on an earlier patch from Zhang Rui.
However, while the previous work was mainly focused on thermal monitoring
the focus here is on the usability from user space perspective.
References: https://lkml.org/lkml/2011/5/26/93
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2013-10-18 01:28:35 +08:00
|
|
|
config INTEL_RAPL
|
|
|
|
|
tristate "Intel RAPL Support"
|
2014-11-13 02:50:36 +08:00
|
|
|
depends on X86 && IOSF_MBI
|
PowerCap: Introduce Intel RAPL power capping driver
The Intel Running Average Power Limit (RAPL) technology provides platform
software with the ability to monitor, control, and get notifications on
power usage.
This feature is present in all Sandy Bridge and later Intel processors.
Newer models allow more fine grained controls to be applied. In RAPL,
power control is divided into domains, which include package, DRAM
controller, CPU core (Power Plane 0), graphics uncore (power plane 1), etc.
The purpose of this driver is to expose the RAPL settings to userspace.
Overall, RAPL fits in the new powercap class driver in that platform
level power capping controls are exposed via this generic interface.
This driver is based on an earlier patch from Zhang Rui.
However, while the previous work was mainly focused on thermal monitoring
the focus here is on the usability from user space perspective.
References: https://lkml.org/lkml/2011/5/26/93
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2013-10-18 01:28:35 +08:00
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
This enables support for the Intel Running Average Power Limit (RAPL)
|
|
|
|
|
technology which allows power limits to be enforced and monitored on
|
|
|
|
|
modern Intel processors (Sandy Bridge and later).
|
|
|
|
|
|
|
|
|
|
In RAPL, the platform level settings are divided into domains for
|
|
|
|
|
fine grained control. These domains include processor package, DRAM
|
|
|
|
|
controller, CPU core (Power Plance 0), graphics uncore (Power Plane
|
|
|
|
|
1), etc.
|
2013-10-12 07:54:56 +08:00
|
|
|
|
|
|
|
|
endif
|
