From: Erik Slagter <erik@slagter.name>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-kernel@vger.kernel.org, Jim serio <jseriousenet@gmail.com>,
Andrew Haninger <ahaning@gmail.com>
Subject: Re: C2/C3 on SMP [Was: Re: 2.6.X not recognizing second CPU]
Date: Wed, 29 Jun 2005 09:40:45 +0200 [thread overview]
Message-ID: <1120030846.7429.32.camel@localhost.localdomain> (raw)
In-Reply-To: <20050628212905.GA31610@isilmar.linta.de>
On Tue, 2005-06-28 at 23:29 +0200, Dominik Brodowski wrote:
> On Tue, Jun 28, 2005 at 01:32:59PM +0200, Erik Slagter wrote:
> > On Mon, 2005-06-27 at 23:42 +0200, Dominik Brodowski wrote:
> > > a) Power Management is available on SMP, though support for it is a bit less
> > > wide-spread than it is for UP
> >
> > Still no C2/C3 handling :-(
>
> Uh, wasn't there a small, nice patch implementing this in bk-acpi a few
> weeks ago?
> *clicketyclick* Oh yes,
> http://bugzilla.kernel.org/show_bug.cgi?id=4401
> states it was merged into bk-acpi-test on 2005-04-22. However, I can't find
> it in current -mm any more...
You're probably talking about the amd768 module. I could use it, but I
never got it working correctly, there is no actual power reduction. It
may have to do with the fast (1000 Hz) 2.6 clock though, making it sleep
in C2/C3 for only very short intervals. Also the selection for idle
CPU's seems to be too simple.
next prev parent reply other threads:[~2005-06-29 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 18:52 2.6.X not recognizing second CPU Jim serio
2005-06-27 19:35 ` Andrew Haninger
[not found] ` <3642108305062713487326b672@mail.gmail.com>
2005-06-27 21:02 ` Andrew Haninger
2005-06-27 21:42 ` Dominik Brodowski
2005-06-27 21:52 ` Jim serio
2005-06-28 11:32 ` Erik Slagter
2005-06-28 21:29 ` C2/C3 on SMP [Was: Re: 2.6.X not recognizing second CPU] Dominik Brodowski
2005-06-29 7:40 ` Erik Slagter [this message]
2005-06-29 8:07 ` Dominik Brodowski
2005-06-29 8:18 ` Erik Slagter
-- strict thread matches above, loose matches on Subject: below --
2005-06-28 21:43 Brown, Len
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=1120030846.7429.32.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=ahaning@gmail.com \
--cc=jseriousenet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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