From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Fix up power managment in 2.6
Date: 3 Sep 2003 17:59:09 GMT [thread overview]
Message-ID: <bj5a5d$8b8$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20030903174904.GH30629@atrey.karlin.mff.cuni.cz
In article <20030903174904.GH30629@atrey.karlin.mff.cuni.cz>,
Pavel Machek <pavel@suse.cz> wrote:
| Hi!
|
| > > -void software_resume(void)
| > > +int __init swsusp_restore(void)
| > > {
| > > - if (num_online_cpus() > 1) {
| > > - printk(KERN_WARNING "Software Suspend has
| > > malfunctioning SMP support. Disabled :(\n");
| > > - return;
| > > - }
| > >
| > > I can not easily see where you moved this check.
| >
| > Read the rest of the patches, and the changelogs (I do believe it's in
| > them). It's in kernel/power/main.c::enter_state(), so all PM handlers can
| > use it.
|
| Notice that this is done during resume. You are free to suspend with 1
| cpu, then attempt to resume with 2 cpus. Not *too* likely to happen,
| but....
Would it matter if you did? Unless you are running an SMP kernel? I
guess at some point the laptop CPUs will have HT, and SMP will be more
of an issue than it is now.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-09-03 18:09 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 23:28 Fix up power managment in 2.6 Pavel Machek
2003-09-01 6:57 ` Russell King
2003-09-01 8:11 ` Pavel Machek
2003-09-01 8:26 ` Russell King
2003-09-01 9:33 ` Pavel Machek
2003-09-01 16:28 ` Linus Torvalds
2003-09-01 21:12 ` Pavel Machek
2003-09-01 21:52 ` Russell King
2003-09-01 22:19 ` Pavel Machek
2003-09-01 22:30 ` Russell King
2003-09-01 22:40 ` Pavel Machek
2003-09-01 22:48 ` Russell King
2003-09-02 17:17 ` Greg KH
2003-09-03 15:13 ` Pavel Machek
2003-09-02 10:21 ` Benjamin Herrenschmidt
2003-09-03 13:02 ` Alan Cox
2003-09-03 13:31 ` Benjamin Herrenschmidt
2003-09-03 17:08 ` Pavel Machek
2003-09-05 20:42 ` Pavel Machek
2003-09-01 22:55 ` Patrick Mochel
2003-09-01 23:38 ` Pavel Machek
2003-09-02 0:52 ` Patrick Mochel
2003-09-02 9:02 ` Pavel Machek
2003-09-02 9:47 ` Pavel Machek
2003-09-02 16:11 ` Patrick Mochel
2003-09-03 16:21 ` Pavel Machek
2003-09-03 23:17 ` Patrick Mochel
2003-09-03 17:49 ` Pavel Machek
2003-09-03 17:59 ` bill davidsen [this message]
2003-09-03 23:20 ` Patrick Mochel
2003-09-05 9:33 ` Pavel Machek
2003-09-03 20:03 ` Bill Davidsen
2003-09-03 22:14 ` Pavel Machek
2003-09-04 4:06 ` Bill Davidsen
2003-09-04 14:52 ` Patrick Mochel
2003-09-02 10:29 ` Jan Rychter
2003-09-05 5:58 ` Rob Landley
2003-09-05 10:26 ` Pavel Machek
2003-09-05 10:56 ` Michael Frank
2003-09-05 11:08 ` Pavel Machek
2003-09-05 11:51 ` Michael Frank
2003-09-05 12:01 ` Pavel Machek
2003-09-05 17:47 ` Patrick Mochel
2003-09-05 18:02 ` Jeff Garzik
2003-09-05 18:13 ` Patrick Mochel
2003-09-05 21:46 ` Jeff Garzik
2003-09-05 18:57 ` Rob Landley
2003-09-05 19:06 ` Pavel Machek
2003-09-05 20:09 ` Keyboard stuff (was Re: Fix up power managment in 2.6) Rob Landley
2003-09-05 20:31 ` Pavel Machek
2003-09-05 20:01 ` Fix up power managment in 2.6 Richard A Nelson
2003-09-05 21:45 ` Jeff Garzik
2003-09-05 18:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:13 Nicolas Mailhot
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='bj5a5d$8b8$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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