From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: James D Strandboge <jstrand1-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org>
Cc: ACPI-Devel
<Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: performance problems?
Date: Tue, 19 Nov 2002 18:11:20 +0100 [thread overview]
Message-ID: <20021119171120.GI691@poup.poupinou.org> (raw)
In-Reply-To: <1037721583.1432.12.camel-Ty44UuN9vPJ5T2F9fCU5s856D9/Od9gv@public.gmane.org>
On Tue, Nov 19, 2002 at 10:59:43AM -0500, James D Strandboge wrote:
> On Tue, 2002-11-19 at 09:54, Markus Gaugusch wrote:
> > On Nov 19, Loic Jaquemet <ljaquemet-BNG0eM9rGRi0IRkH3yUr9EW4647UYGdYQQ4Iyu8u01E@public.gmane.org> wrote:
> > > i'am using 2.4.19 + around october patch ( I'll check that this evening )
> > > on sony vaio fx502
> > > [...]
> > > when I fetch the /proc/acpi/<batteriesxxx>/state|info files, I get a 1-2
> > > second freeze| lag ..
> > > [...]
> > > I'm not sure, but i think i didn't have this problem on pre-september
> > > patches ..
> > No, it has been present before. I have an FX405 and can't use any battery
> > monitor applet that reads the info file. Even a 'cat
> > /proc/acpi/battery/BAT1/info' causes a noticable peak in my cpu monitor
> > (kernel time). At least, it doesn't freeze keyboard anymore, thanks to the
> > ACPI people!
> >
>
> You want to poll /proc/acpi/battery/BAT1/state or whatever is correct
> for your battery. Polling info requires interrupts with the BIOS I
> think, and state is there for a quick poll. At least on my machine this
> is the case.
Yes and not. In fact, the ASL code contains some Notification() methods, then
kernel will inform user space via /proc/acpi/event.
Most of the time, those Notification() are generated by an interrupt (certainly
an SCI).
You should see some Notification() to the battery(ies) in a \_GPE.[EL]xx(), or in a
_Qxx() from an embedded controller in that case.
>
> Perhaps someone would want to clarify the difference and why info causes
> a hang and state does not.
info give 'static' informations, as design capacity, last full technology, etc.
It is 'huge', and do not need to be read often.
state give the actual remaining capacity of the battery, present voltage, and so
on. It is 'small' and also hold the 'variable' part of the battery.
Now why cat'ing 'info' hang some systems is another
problem (Should Not Happen (c)(tm))...
--
Ducrot Bruno
http://www.poupinou.org Page profaissionelle
http://toto.tu-me-saoules.com Haume page
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
next prev parent reply other threads:[~2002-11-19 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 13:37 performance problems? Thomas List
2002-11-19 13:54 ` Loic Jaquemet
[not found] ` <3DDA42A3.35F6BFE1-BNG0eM9rGRi0IRkH3yUr9EW4647UYGdYQQ4Iyu8u01E@public.gmane.org>
2002-11-19 14:54 ` Markus Gaugusch
[not found] ` <Pine.LNX.4.44.0211191552030.31104-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2002-11-19 15:59 ` James D Strandboge
[not found] ` <1037721583.1432.12.camel-Ty44UuN9vPJ5T2F9fCU5s856D9/Od9gv@public.gmane.org>
2002-11-19 17:11 ` Ducrot Bruno [this message]
2002-11-19 16:39 ` Thomas List
2002-12-16 8:06 ` Malte Thoma
[not found] ` <3DDA3E96.50906-vA1bhqPz9FBZXbeN9DUtxg@public.gmane.org>
2002-11-19 14:01 ` Nils Faerber
2002-11-19 14:40 ` David Douard
[not found] ` <200211191540.58738.douard-nJJpUPIbDOA@public.gmane.org>
2002-11-19 15:23 ` Ducrot Bruno
2002-11-19 16:00 ` Thomas List
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 19:22 Grover, Andrew
[not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A520-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-11-19 21:16 ` Thomas List
2002-11-19 22:29 ` Markus Gaugusch
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=20021119171120.GI691@poup.poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jstrand1-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox