From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Radivoje Jovanovic <radivoje.jovanovic@intel.com>,
Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>,
Mathias Krause <minipli@googlemail.com>,
Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>
Subject: [PATCH 0/3] powercap, intel_rapl, implement time window checks
Date: Tue, 15 Dec 2015 08:02:09 -0500 [thread overview]
Message-ID: <1450184532-21150-1-git-send-email-prarit@redhat.com> (raw)
The Intel ASDM provides a maximum time window that can be specified when
setting a time window in the RAPL driver. While the ASDM doesn't explicitly
provide a minimum time window value, it does provide a minimum time window
unit that also can be used as a minimum value.
This patchset implements barrier checking for the time windows, and adds
reporting of a known bug in which the maxmimum time window value may be
erroneously set to 0, as well as a module parameter to avoid the maximum
window checks on broken BIOSes.
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Radivoje Jovanovic <radivoje.jovanovic@intel.com>
Cc: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>
Cc: Mathias Krause <minipli@googlemail.com>
Cc: Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Prarit Bhargava (3):
powercap, intel_rapl, implement get_max_time_window
powercap, intel_rapl, implement check for minimum time window
powercap, intel_rapl, Add ignore_max_window_check module parameter
for broken BIOSes
drivers/powercap/intel_rapl.c | 51 +++++++++++++++++++++++++++++++++++++++
drivers/powercap/powercap_sys.c | 6 +++--
2 files changed, 55 insertions(+), 2 deletions(-)
--
1.7.9.3
next reply other threads:[~2015-12-15 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 13:02 Prarit Bhargava [this message]
2015-12-15 13:02 ` [PATCH 1/3] powercap, intel_rapl, implement get_max_time_window Prarit Bhargava
2015-12-17 5:45 ` Seiichi Ikarashi
2015-12-17 12:26 ` Prarit Bhargava
2015-12-15 13:02 ` [PATCH 2/3] powercap, intel_rapl, implement check for minimum time window Prarit Bhargava
2015-12-15 13:02 ` [PATCH 3/3] powercap, intel_rapl, Add ignore_max_window_check module parameter for broken BIOSes Prarit Bhargava
2015-12-18 5:50 ` Seiichi Ikarashi
2015-12-18 12:23 ` Prarit Bhargava
2015-12-21 14:50 ` [PATCH 0/3 v2] powercap, intel_rapl, implement time window checks Prarit Bhargava
2015-12-21 14:50 ` [PATCH 1/3] powercap, intel_rapl, implement get_max_time_window Prarit Bhargava
2015-12-21 14:50 ` [PATCH 2/3] powercap, intel_rapl, implement check for minimum time window Prarit Bhargava
2015-12-21 14:50 ` [PATCH 3/3] powercap, intel_rapl, Add ignore_max_time_window_check module parameter for broken BIOSes Prarit Bhargava
-- strict thread matches above, loose matches on Subject: below --
2016-01-21 16:15 [PATCH 0/3] powercap, intel_rapl, implement time window checks Prarit Bhargava
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=1450184532-21150-1-git-send-email-prarit@redhat.com \
--to=prarit@redhat.com \
--cc=ajay.thomas.david.rajamanickam@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=radivoje.jovanovic@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=s.ikarashi@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).