| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 24 Oct 2006 04:27:04 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Shem Multinymous <multinymous@...il.com> Cc: David Zeuthen <davidz@...hat.com>, David Woodhouse <dwmw2@...radead.org>, linux-kernel@...r.kernel.org, olpc-dev@...top.org, greg@...ah.com, len.brown@...el.com, sfr@...b.auug.org.au, benh@...nel.crashing.org Subject: Re: Battery class driver. 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@...f.ucam.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists