| Srinivas Pandruvada | 75d2364 | 2013-10-11 16:54:56 -0700 | [diff] [blame] | 1 | # |
| 2 | # Generic power capping sysfs interface configuration |
| 3 | # |
| 4 | |
| 5 | menuconfig POWERCAP |
| 6 | bool "Generic powercap sysfs driver" |
| 7 | help |
| 8 | The power capping sysfs interface allows kernel subsystems to expose power |
| 9 | capping settings to user space in a consistent way. Usually, it consists |
| 10 | of multiple control types that determine which settings may be exposed and |
| 11 | power zones representing parts of the system that can be subject to power |
| 12 | capping. |
| 13 | |
| 14 | If you want this code to be compiled in, say Y here. |
| 15 | |
| 16 | if POWERCAP |
| 17 | # Client driver configurations go here. |
| Jacob Pan | 2d281d8 | 2013-10-17 10:28:35 -0700 | [diff] [blame] | 18 | config INTEL_RAPL |
| 19 | tristate "Intel RAPL Support" |
| 20 | depends on X86 |
| 21 | default n |
| 22 | ---help--- |
| 23 | This enables support for the Intel Running Average Power Limit (RAPL) |
| 24 | technology which allows power limits to be enforced and monitored on |
| 25 | modern Intel processors (Sandy Bridge and later). |
| 26 | |
| 27 | In RAPL, the platform level settings are divided into domains for |
| 28 | fine grained control. These domains include processor package, DRAM |
| 29 | controller, CPU core (Power Plance 0), graphics uncore (Power Plane |
| 30 | 1), etc. |
| Srinivas Pandruvada | 75d2364 | 2013-10-11 16:54:56 -0700 | [diff] [blame] | 31 | |
| 32 | endif |