All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>
To: Prarit Bhargava <prarit@redhat.com>, <linux-kernel@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Radivoje Jovanovic <radivoje.jovanovic@intel.com>,
	Mathias Krause <minipli@googlemail.com>,
	Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>
Subject: Re: [PATCH 3/3] powercap, intel_rapl, Add ignore_max_time_window_check module parameter for broken BIOSes
Date: Fri, 22 Jan 2016 09:28:24 +0900	[thread overview]
Message-ID: <56A177A8.2020600@jp.fujitsu.com> (raw)
In-Reply-To: <1453392910-9549-4-git-send-email-prarit@redhat.com>

On 2016-01-22 01:15, Prarit Bhargava wrote:
> Some systems erroneously set the maximum time window field of
> MSR_PKG_POWER_INFO register to 0.  This results in a user not being able
> to set the time windows for the package.  In some cases, however, RAPL
> will still continue to work with a small window (albeit through some
> trial and error).  This patch adds a ignore_max_time_window_check module
> parameter to avoid the maximum time window check in set_time_window().
> 
> [v2]: change name to max_time_window_check, fix (val == 0) check
> 
> 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>
> ---
>  drivers/powercap/intel_rapl.c |   18 +++++++++++++++---
>  1 file changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
> index 14753e5..939026d 100644
> --- a/drivers/powercap/intel_rapl.c
> +++ b/drivers/powercap/intel_rapl.c
> @@ -505,13 +505,24 @@ static int get_max_time_window(struct powercap_zone *power_zone, int id,
>  
>  	if (rapl_read_data_raw(rd, MAX_TIME_WINDOW, true, &val))
>  		ret = -EIO;
> -	else
> +	else {
>  		*data = val;
> -
> +		if (val == 0)
> +			pr_warn_once(FW_BUG "intel_rapl: Maximum Time Window is zero.  This is a BIOS bug that should be reported to your hardware or BIOS vendor.  The value of zero may prevent Intel RAPL from functioning properly.  Most bugs can be avoided by setting the ignore_max_window_check module parameter.\n");

                                                                                                                                                                                                                                                                                 The correct name is ignore_max_time_window_check here.

--
Seiichi

  reply	other threads:[~2016-01-22  0:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 16:15 [PATCH 0/3] powercap, intel_rapl, implement time window checks Prarit Bhargava
2016-01-21 16:15 ` [PATCH 1/3] powercap, intel_rapl, implement get_max_time_window Prarit Bhargava
2016-01-22  0:27   ` Seiichi Ikarashi
2016-01-22 16:26     ` Prarit Bhargava
2016-01-21 16:15 ` [PATCH 2/3] powercap, intel_rapl, implement check for minimum time window Prarit Bhargava
2016-01-21 16:15 ` [PATCH 3/3] powercap, intel_rapl, Add ignore_max_time_window_check module parameter for broken BIOSes Prarit Bhargava
2016-01-22  0:28   ` Seiichi Ikarashi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-15 13:02 [PATCH 0/3] powercap, intel_rapl, implement time window checks Prarit Bhargava
2015-12-21 14:50 ` [PATCH 0/3 v2] " 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

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=56A177A8.2020600@jp.fujitsu.com \
    --to=s.ikarashi@jp.fujitsu.com \
    --cc=ajay.thomas.david.rajamanickam@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minipli@googlemail.com \
    --cc=prarit@redhat.com \
    --cc=radivoje.jovanovic@intel.com \
    --cc=rafael.j.wysocki@intel.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.