From: "Joseph P. Garcia" <jpgarcia@execpc•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: joker@cymes•de, linuxppc-dev@lists•linuxppc.org
Subject: Re: Design weakness in /proc/pmu ?!
Date: Thu, 18 Apr 2002 15:56:10 -0500 [thread overview]
Message-ID: <20020418155610.28459dcc.jpgarcia@execpc.com> (raw)
In-Reply-To: <20020418183148.25976@smtp.wanadoo.fr>
Greetings Ben, Matthias, and others.
On Thu, 18 Apr 2002 20:31:47 +0200
Benjamin Herrenschmidt <benh@kernel•crashing.org> wrote:
> It's difficult to find a suitable answer. The time remaining is
> obtained directly from the PMU on newer machines, we don't really
> have the proper algorithm to calculate it on these, what
> machine did you get those dumps from ? We may simply have a bug
> on older machine calculation causing that 0, in which case it
> has to be fixed.
Each battery in the current code is handled seperately. Each battery has
its own value for current. A battery not in use has a value of 0, which
the time calculations handle by saying 0 time left, as if you're plugged in
and not charging, this is what would be expected.
So its not really a bug, just an implemenetation decision that mirrors the
hardware. But I'm all for Matthias' suggestion. The alternative is to do
what I had the gkrellm pmu plugin do. (without letting it know how to
redundantly find the time on its own just using ratios, but that assumes a
linear function)
--
Joseph P. Garcia http://www.lycestra.com/ http://lidar.ssec.wisc.edu/
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-18 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 18:47 Design weakness in /proc/pmu ?! Matthias Grimm
2002-04-18 18:31 ` Benjamin Herrenschmidt
2002-04-18 20:56 ` Joseph P. Garcia [this message]
2002-04-19 16:32 ` Matthias Grimm
2002-04-19 17:06 ` Benjamin Herrenschmidt
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=20020418155610.28459dcc.jpgarcia@execpc.com \
--to=jpgarcia@execpc$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=joker@cymes$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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