mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Radivoje Jovanovic <radivoje.jovanovic@intel.com>,
	Mathias Krause <minipli@googlemail.com>,
	Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>
Subject: Re: [PATCH] powercap, intel_rapl.c, fix BIOS lock check
Date: Wed, 09 Dec 2015 08:27:05 -0500	[thread overview]
Message-ID: <56682C29.8050207@redhat.com> (raw)
In-Reply-To: <566771EC.2020201@jp.fujitsu.com>



On 12/08/2015 07:12 PM, Seiichi Ikarashi wrote:
> On 2015-12-09 03:33, Prarit Bhargava wrote:
>> Intel RAPL initialized on several systems where the BIOS lock bit (msr
>> 0x610, bit 63) was set.  This occured because the return value of
>> rapl_read_data_raw() was being checked, rather than the value of the variable
>> passed in, locked.
>>
>> This patch properly implments the rapl_read_data_raw() call to check the
>> variable locked, and now the Intel RAPL driver outputs the warning:
>>
>> 	intel_rapl: RAPL package 0 domain package locked by BIOS
>>
>> and does not initialize for the package.
>>
>> Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
>> Cc: Jacob Pan <jacob.jun.pan@linux.intel.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 |    6 ++++--
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
>> index cc97f08..0b0d09d 100644
>> --- a/drivers/powercap/intel_rapl.c
>> +++ b/drivers/powercap/intel_rapl.c
>> @@ -1341,11 +1341,13 @@ static int rapl_detect_domains(struct rapl_package *rp, int cpu)
>>  
>>  	for (rd = rp->domains; rd < rp->domains + rp->nr_domains; rd++) {
>>  		/* check if the domain is locked by BIOS */
>> -		if (rapl_read_data_raw(rd, FW_LOCK, false, &locked)) {
>> +		ret = rapl_read_data_raw(rd, FW_LOCK, false, &locked);
>> +		if (ret)
>> +			return ret;
>> +		if (locked)
>>  			pr_info("RAPL package %d domain %s locked by BIOS\n",
>>  				rp->id, rd->name);
>>  				rd->state |= DOMAIN_STATE_BIOS_LOCKED;
>> -		}
>>  	}
> 
> A good spot!
> But this patch looks setting DOMAIN_STATE_BIOS_LOCKED bit to all package domains.
> I suppose what you are going to do is like below.
> 
> --- a/drivers/powercap/intel_rapl.c	2015-11-02 09:05:25.000000000 +0900
> +++ b/drivers/powercap/intel_rapl.c	2015-12-09 09:05:33.386142840 +0900
> @@ -1340,10 +1340,13 @@ static int rapl_detect_domains(struct ra
>  
>  	for (rd = rp->domains; rd < rp->domains + rp->nr_domains; rd++) {
>  		/* check if the domain is locked by BIOS */
> -		if (rapl_read_data_raw(rd, FW_LOCK, false, &locked)) {
> +		ret = rapl_read_data_raw(rd, FW_LOCK, false, &locked);
> +		if (ret)
> +			return ret;
> +		if (locked) {
>  			pr_info("RAPL package %d domain %s locked by BIOS\n",
>  				rp->id, rd->name);
> -				rd->state |= DOMAIN_STATE_BIOS_LOCKED;
> +			rd->state |= DOMAIN_STATE_BIOS_LOCKED;
>  		}
>  	}

Oh geez :)  Of course ... I'll resubmit shortly.

P.

>  
> 

      reply	other threads:[~2015-12-09 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 18:33 Prarit Bhargava
2015-12-08 23:30 ` Jacob Pan
2015-12-09  0:12 ` Seiichi Ikarashi
2015-12-09 13:27   ` Prarit Bhargava [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=56682C29.8050207@redhat.com \
    --to=prarit@redhat.com \
    --cc=ajay.thomas.david.rajamanickam@intel.com \
    --cc=jacob.jun.pan@linux.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

Powered by JetHome