From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org,
len.brown@intel.com, rjw@sisk.pl, arjan@linux.intel.com,
jacob.jun.pan@linux.intel.com,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v3 0/6] Power Capping Framework and RAPL Driver
Date: Fri, 11 Oct 2013 16:54:54 -0700 [thread overview]
Message-ID: <1381535700-2408-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
Overview
With the evolution of technologies, which enables power monitoring and limiting,
more and more devices are able to constrain their power consumption under certain
limits. There are several use cases for such technologies:
- Power monitoring: Each device can report its power consumption.
- Power Limiting: Setting power limits on the devices allows users to guard against
platform reaching max system power level.
- Maximize performance: While staying below a power limit, it allows devices to
automatically adjust performance to meet demands
- Dynamic control and re-budgeting: If each device can be constrained to some power,
extra power can redistributed to other devices, which needs additional performance.
One such example of technologies is RAPL (Running Average Power Limit) mechanism
available in the latest Intel processors. Intel is slowly adding many devices under
RAPL control. Also there are other technologies available, for power capping various
devices. Soon it is very likely that other vendors are also adding or considering
such implementation.
Power Capping framework is an effort to have a uniform interface available to Linux
drivers, which will enable
- A uniform sysfs interface for all devices which can offer power capping
- A common API for drivers, which will avoid code duplication and easy
implementation of client drivers.
Also submitting Intel RAPL driver using power capping framework.
History:
v3
As suggested changed DEVICE_ATTR to DEVICE_ATTR_RO/RW
Minor change in RAPL driver for TIME_WINDOW1_MASK to change to ULL
v2
As suggested, added BIT_ULL_MASK and BIT_ULL_WORD
v1
Incorporated changes suggested during RFC stage
Jacob Pan (2):
x86/msr: add 64bit _on_cpu access functions
Introduce Intel RAPL power capping driver
Srinivas Pandruvada (4):
PowerCap: Documentation
PowerCap: Add class driver
PowerCap: Added to drivers build
bitops: Introduce BIT_ULL
Documentation/ABI/testing/sysfs-class-powercap | 152 +++
Documentation/power/powercap/powercap.txt | 236 ++++
arch/x86/include/asm/msr.h | 22 +
arch/x86/lib/msr-smp.c | 62 ++
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/powercap/Kconfig | 31 +
drivers/powercap/Makefile | 2 +
drivers/powercap/intel_rapl.c | 1395 ++++++++++++++++++++++++
drivers/powercap/powercap_sys.c | 683 ++++++++++++
include/linux/bitops.h | 3 +
include/linux/powercap.h | 325 ++++++
12 files changed, 2914 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-class-powercap
create mode 100644 Documentation/power/powercap/powercap.txt
create mode 100644 drivers/powercap/Kconfig
create mode 100644 drivers/powercap/Makefile
create mode 100644 drivers/powercap/intel_rapl.c
create mode 100644 drivers/powercap/powercap_sys.c
create mode 100644 include/linux/powercap.h
--
1.8.3.1
next reply other threads:[~2013-10-11 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 23:54 Srinivas Pandruvada [this message]
2013-10-11 23:54 ` [PATCH v3 1/6] PowerCap: Documentation Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 2/6] PowerCap: Add class driver Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 3/6] PowerCap: Added to drivers build Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 4/6] x86/msr: add 64bit _on_cpu access functions Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 5/6] bitops: Introduce BIT_ULL Srinivas Pandruvada
2013-10-11 23:55 ` [PATCH v3 6/6] Introduce Intel RAPL power capping driver Srinivas Pandruvada
2013-10-16 22:41 ` [PATCH v3 0/6] Power Capping Framework and RAPL Driver Rafael J. Wysocki
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=1381535700-2408-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).