All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"prarit@redhat.com" <prarit@redhat.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>
Cc: "Jovanovic, Radivoje" <radivoje.jovanovic@intel.com>,
	"s.ikarashi@jp.fujitsu.com" <s.ikarashi@jp.fujitsu.com>,
	"David Rajamanickam,
	Ajay Thomas" <ajay.thomas.david.rajamanickam@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"minipli@googlemail.com" <minipli@googlemail.com>
Subject: Re: [RESEND PATCH 0/3 v4] powercap, intel_rapl, implement time window checks
Date: Mon, 28 Mar 2016 18:07:36 +0000	[thread overview]
Message-ID: <1459188473.13525.33.camel@intel.com> (raw)
In-Reply-To: <1458563236-19269-1-git-send-email-prarit@redhat.com>

+Jacob

On Mon, 2016-03-21 at 08:27 -0400, Prarit Bhargava wrote:
> This was submitted back in December and not picked up after review.
> 
> P.
> 
> -----8<----
> 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_time_window_check module
>     parameter for broken BIOSes
> 
>  drivers/powercap/intel_rapl.c   |   50
> +++++++++++++++++++++++++++++++++++++++
>  drivers/powercap/powercap_sys.c |    6 +++--
>  2 files changed, 54 insertions(+), 2 deletions(-)
> 

      parent reply	other threads:[~2016-03-28 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 12:27 [RESEND PATCH 0/3 v4] powercap, intel_rapl, implement time window checks Prarit Bhargava
2016-03-21 12:27 ` [PATCH 1/3 v4] powercap, intel_rapl, implement get_max_time_window Prarit Bhargava
2016-03-31 18:28   ` Pandruvada, Srinivas
2016-04-05 13:14     ` Prarit Bhargava
2016-04-11 11:33     ` Prarit Bhargava
2016-04-11 14:11       ` Pandruvada, Srinivas
2016-03-21 12:27 ` [PATCH 2/3 v4] powercap, intel_rapl, implement check for minimum time window Prarit Bhargava
2016-03-21 12:27 ` [PATCH 3/3 v3] powercap, intel_rapl, Add ignore_max_time_window_check module parameter for broken BIOSes Prarit Bhargava
2016-03-28 18:07 ` Pandruvada, Srinivas [this message]

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=1459188473.13525.33.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=ajay.thomas.david.rajamanickam@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=minipli@googlemail.com \
    --cc=prarit@redhat.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 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.