From: Pavel Machek <pavel@suse.cz>
To: "Theodore Ts'o" <tytso@mit.edu>, Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Daniel Petrini <d.pensator@gmail.com>,
Tony Lindgren <tony@atomide.com>,
vatsa@in.ibm.com, ck list <ck@vds.kolivas.org>,
Adam Belay <abelay@novell.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: Re: [PATCH] i386 No Idle HZ aka dynticks 051221
Date: Tue, 27 Dec 2005 00:27:12 +0100 [thread overview]
Message-ID: <20051226232712.GH1974@elf.ucw.cz> (raw)
In-Reply-To: <20051226225246.GA9915@thunk.org>
On Po 26-12-05 17:52:48, Theodore Ts'o wrote:
> On Mon, Dec 26, 2005 at 09:38:06PM +0100, Pavel Machek wrote:
> > Stupid IBM. I've seen it appearing/disappearing, but did not work out
> > when.
> >
> > No-C4-on-AC is bad -- if you just disconnect AC and walk away, you are
> > running without benefits of C4. Bad. Changing benchmarks depending on
> > you booting on AC or battery also look nasty.
>
> The moment you disconnect AC, it C4 automagically appears. When you
> reconnect to the AC mains, the C4 state disappears again, at least
> from the listing displayed by /proc/acpi/processor/CPU0/power. So the
> first issue you brought up isn't a problem.
It does not seem to work like that here. I'm not sure what the exact
rules are, but I know that I sometimes have C4 and sometimes not. I
have C4 now, and it is used, even when I'm on AC power. Thinkpad X32.
> More of an issue is that there are times when the laptop might think
> that it's running of the AC mains, but in fact the owner may have
> connected an external battery, and might _want_ the system to be as
> frugal as possible with the power.
Yes... OTOH it is not that bad -- we could simply hardcode data from
acpi BIOS into kernel, ignore what ACPI says, and drive C4 even on AC
power. But that would be hack (tm).
> Whether I boot from AC power battery seems to be immaterial; what
> seems to matter is whether or not the laptop is running on battery at
> the moment that /proc/acpi/processor/CPU0/power is sampled.
I did not realize ACPI was _that_ clever. Anyway, it is different on
my machine...
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-12-26 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 16:10 Con Kolivas
2005-12-20 17:27 ` Jan De Luyck
2005-12-20 19:39 ` Daniel Petrini
2005-12-20 20:46 ` Jan De Luyck
2005-12-25 17:16 ` Theodore Ts'o
2005-12-26 2:55 ` Theodore Ts'o
2005-12-26 18:47 ` Matthew Garrett
2005-12-26 18:56 ` Theodore Ts'o
2005-12-26 20:03 ` Dominik Brodowski
2005-12-26 20:38 ` Pavel Machek
2005-12-26 22:52 ` Theodore Ts'o
2005-12-26 23:27 ` Pavel Machek [this message]
2005-12-27 14:03 ` Pavel Machek
2005-12-27 14:22 ` C4 strangeness [was Re: [PATCH] i386 No Idle HZ aka dynticks 051221] Pavel Machek
2005-12-27 15:33 ` C4 non-strangeness [was: " Dominik Brodowski
2005-12-27 16:13 ` Pavel Machek
2005-12-26 22:19 ` [PATCH] i386 No Idle HZ aka dynticks 051221 Dominik Brodowski
2005-12-27 0:33 ` Theodore Ts'o
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=20051226232712.GH1974@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=abelay@novell.com \
--cc=ck@vds.kolivas.org \
--cc=d.pensator@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tony@atomide.com \
--cc=tytso@mit.edu \
--cc=vatsa@in.ibm.com \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®