linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>, "Kenneth R. Crudup" <kenny@panix.com>
Cc: linux-pm@lists.linux-foundation.org, rafael.j.wysocki@intel.com,
	linux-pm@vger.kernel.org, "Liang, Kan" <kan.liang@intel.com>
Subject: Re: Why do I sometimes "lose" the "psys" RAPL counter?
Date: Mon, 30 Mar 2020 21:55:51 -0700	[thread overview]
Message-ID: <78d89a67d7fdda477fe406d5401a50b892d2ee81.camel@linux.intel.com> (raw)
In-Reply-To: <a72bd97c2d0a3d1b9438198db79bfecaaf2918b3.camel@intel.com>

On Tue, 2020-03-31 at 10:49 +0800, Zhang Rui wrote:
> On Mon, 2020-03-30 at 10:40 -0700, Kenneth R. Crudup wrote:
> > On Mon, 30 Mar 2020, Srinivas Pandruvada wrote:
> > 
> > > I could reproduce this. This fails because the Psys MSR read 0. 
> 
> Do you mean MSR_PLATFORM_POWER_LIMIT?
MSR_PLATFORM_ENERGY_COUNTER (0x64d) 

Thanks
Srinivas

> It is not 0 according to previous emails.


> 
> > > Also
> > > the counter values are not correct as the incremental values are
> > > less
> > > than package energy counter values.
> > 
> > OK, so the very night I'd asked this question, Dell put out a BIOS
> > update
> > (BIOS 1.3.1 03/02/2020) that seems to have fixed this issue; I have
> > not
> > had a missing "psys" domain since updating. Srinivas, can you
> > update
> > the
> > XPS 7390 you have to this BIOS version and verify this is fixed?
> > 
> Good to know.
> 
> thanks,
> rui
> 
> 


  reply	other threads:[~2020-03-31  4:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.21.2003252212220.2971@xps-7390>
2020-03-26  5:30 ` Why do I sometimes "lose" the "psys" RAPL counter? Kenneth R. Crudup
2020-03-26  8:13   ` Rafael J. Wysocki
2020-03-26 15:23     ` Srinivas Pandruvada
     [not found] ` <691eb7a6efd7a954295f234a70f548fd0c81e2f8.camel@intel.com>
     [not found]   ` <alpine.DEB.2.21.2003252353370.2971@xps-7390>
     [not found]     ` <7e1562ce93b83a685aa54dd2ae5a5b36c5737cb6.camel@intel.com>
     [not found]       ` <alpine.DEB.2.21.2003260225200.2971@xps-7390>
2020-03-26  9:36         ` Kenneth R. Crudup
2020-03-26  9:54           ` Kenneth R. Crudup
     [not found]       ` <c9a24dfbc765c9c19d87094e5b2044f33431e501.camel@intel.com>
2020-03-26  9:38         ` Kenneth R. Crudup
2020-03-26  9:55           ` Kenneth R. Crudup
2020-03-26 10:15           ` Kenneth R. Crudup
2020-03-30  9:55             ` Zhang Rui
2020-03-30 15:51               ` Srinivas Pandruvada
2020-03-30 17:40                 ` Kenneth R. Crudup
2020-03-31  2:49                   ` Zhang Rui
2020-03-31  4:55                     ` Srinivas Pandruvada [this message]
     [not found] <20200326181641.291505803E3@linux.intel.com>
2020-03-26 19:36 ` Srinivas Pandruvada
     [not found]   ` <alpine.DEB.2.21.2003261303530.3213@xps-7390>
2020-03-27 16:57     ` Srinivas Pandruvada
2020-03-27 17:09       ` Kenneth R. Crudup
2020-03-27 19:19         ` Srinivas Pandruvada

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=78d89a67d7fdda477fe406d5401a50b892d2ee81.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=kan.liang@intel.com \
    --cc=kenny@panix.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rui.zhang@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 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).