All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] v2.5-rc1 testing: accounting still very wrong
Date: Mon, 04 Nov 2013 10:31:05 -0800	[thread overview]
Message-ID: <20131104103105.5bb4711b@bluebird.jf.intel.com> (raw)
In-Reply-To: 20131102195015.GJ5519@merlins.org

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

On Sat, 2 Nov 2013 12:50:15 -0700
Marc MERLIN <marc_powertop(a)merlins.org> wrote:

> On Sat, Nov 02, 2013 at 06:48:02AM -0700, Marc MERLIN wrote:
> > On Fri, Oct 18, 2013 at 11:09:26AM -0700, Kristen Carlson Accardi wrote:
> > > Please test.
> > 
> > Still the same power counting bugs than previous versions.
> > After a few minutes, on battery, it went from 12W to 20W because of an
> > rsync in the background, and when that rsync was finished (sigstop), I got this.
> > 
> > Somehow I very much doubt that e17 was using 1550W.
> > 
> > Clearly there is at least an assert missing that should ensure that the list
> > of power estimated values clearly exceeds the total power.
> > 
> > Even if I stop enligthenment, which seems to be most of the wakeups, bad
> > accounting is all wrong in many ways, see below:

Thanks for the detailed report.  I think we aren't going to be able to
address this for the 2.5 release, but I will put it on my list of
things to do to see if we can duplicate this issue on another machine
and start figuring out what is going on.  We'll try to put a test case
for something like this together for the 2.6 release just to confirm
that we are within the realm of possibilities for estimation.


             reply	other threads:[~2013-11-04 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 18:31 Kristen Carlson Accardi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02 19:50 [Powertop] v2.5-rc1 testing: accounting still very wrong Marc MERLIN
2013-11-02 13:48 Marc MERLIN

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=20131104103105.5bb4711b@bluebird.jf.intel.com \
    --to=powertop@lists.01.org \
    /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.