From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Shem Multinymous <multinymous@gmail.com>
Cc: David Zeuthen <davidz@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, olpc-dev@laptop.org,
greg@kroah.com, len.brown@intel.com, sfr@canb.auug.org.au,
benh@kernel.crashing.org
Subject: Re: Battery class driver.
Date: Tue, 24 Oct 2006 04:27:04 +0100 [thread overview]
Message-ID: <20061024032704.GA24320@srcf.ucam.org> (raw)
In-Reply-To: <41840b750610231956ib1c7204tafb23ecd76f5d9d2@mail.gmail.com>
On Tue, Oct 24, 2006 at 04:56:30AM +0200, Shem Multinymous wrote:
> 30 seconds? I've seen battery applets that poll 1sec intervals (that's
> actually useful when you tweak power saving). And for things like the
> hdaps accelerometer driver, we're at the 50HZ region.
Reading the battery status has the potential to call an SMI that might
take an arbitrary period of time to return, and we found that having
querying at around the 1 second mark tended to result in noticable
system performace degredation.
Possibly it would be useful if the kernel could keep track of how long
certain queries take? That would let userspace calibrate itself without
having to worry about whether it was preempted or not.
> You can't require reading battery status to be a root-only operation.
We certainly can. Whether we want to is another matter :) I tend to
agree that moving to a setup that makes it harder for command-line users
to read the battery status would be a regression.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-10-24 3:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:20 Battery class driver David Woodhouse
2006-10-23 18:26 ` Matthew Garrett
2006-10-23 18:30 ` David Woodhouse
2006-10-24 3:36 ` Benjamin Herrenschmidt
2006-10-23 18:30 ` Greg KH
2006-10-23 18:32 ` Greg KH
2006-10-23 18:50 ` David Woodhouse
2006-10-24 3:39 ` Benjamin Herrenschmidt
2006-10-23 21:04 ` Jean Delvare
2006-10-23 22:15 ` David Zeuthen
2006-10-23 22:59 ` Greg KH
2006-10-24 1:31 ` David Zeuthen
2006-10-24 3:04 ` Shem Multinymous
2006-10-24 2:56 ` Shem Multinymous
2006-10-24 3:27 ` Matthew Garrett [this message]
2006-10-24 3:48 ` Benjamin Herrenschmidt
2006-10-24 3:53 ` Matthew Garrett
2006-10-24 5:43 ` Benjamin Herrenschmidt
2006-10-24 11:09 ` Shem Multinymous
2006-10-24 2:04 ` Shem Multinymous
2006-10-25 10:45 ` Pavel Machek
[not found] <1161628327.19446.391.camel@pmac.infradead.org>
2006-10-23 19:18 ` Dan Williams
2006-10-23 19:58 ` Richard Hughes
2006-10-23 20:10 ` Roland Dreier
2006-10-23 20:48 ` David Woodhouse
2006-10-24 3:44 ` Benjamin Herrenschmidt
2006-10-24 17:18 ` Richard Hughes
2006-10-24 3:41 ` 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=20061024032704.GA24320@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=benh@kernel.crashing.org \
--cc=davidz@redhat.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=multinymous@gmail.com \
--cc=olpc-dev@laptop.org \
--cc=sfr@canb.auug.org.au \
/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