mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Bart Samwel <bart@samwel.tk>
Cc: Huw Rogers <count0@localnet.com>,
	linux-kernel@vger.kernel.org, linux-laptop@mobilix.org
Subject: Re: 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0
Date: Tue, 27 Jan 2004 21:58:15 +0100	[thread overview]
Message-ID: <20040127205815.GA19011@elf.ucw.cz> (raw)
In-Reply-To: <401685F9.6000904@samwel.tk>

Hi!

> >>Anyway, sleep/suspend/standby functionality (important to most laptop
> >>users, need to close the lid and go): This checkin to
> >>kernel/power/main.c seems to disable suspend with SMP (!?):
> >>
> >>--- 1.3/kernel/power/main.c	Sat Jan 24 20:44:47 2004
> >>+++ 1.4/kernel/power/main.c	Sat Jan 24 20:44:47 2004
> >>@@ -172,6 +172,12 @@
> >> 	if (down_trylock(&pm_sem))
> >> 		return -EBUSY;
> >>
> >>+	/* Suspend is hard to get right on SMP. */
> >>+	if (num_online_cpus() != 1) {
> >>+		error = -EPERM;
> >>+		goto Unlock;
> >>+	}
> >>+
> >> 	if ((error = suspend_prepare(state)))
> >> 		goto Unlock;
> >>
> >>... which, given the prevalence of hyperthreaded CPUs on laptops, is
> >>fighting a trend. I backed out the above with a #if 0 then tried echo -n
> >>1>/proc/acpi/sleep again. This time I got:
> >
> >
> > Well, no sleep developers have SMP or HT machines, AFAICT.
> >
> > If you back that out... well you are on your own.
> 
> Just a random thought: if I understand it correctly, CPU hotplugging is 
> intended to be able to take CPUs online and offline one by one, am I 
> right? Well, when that infrastructure's ready, this can probably be made 
> to work for SMP by taking all the other CPUs offline first. They're all 
> going to go offline because of the suspend anyway, so it shouldn't make 
> much difference. :)

That was original plan, but CPU hotplug is unlikely to get into 2.6,
AFAICT. (And Nigel has another solution).

								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

      parent reply	other threads:[~2004-01-27 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25  5:26 Huw Rogers
2004-01-25 15:28 ` Zwane Mwaikambo
2004-01-26 23:33 ` bill davidsen
2004-01-27  8:39 ` Pavel Machek
2004-01-27 15:38   ` Bart Samwel
2004-01-27 19:30     ` Nigel Cunningham
     [not found]       ` <37778.199.172.169.20.1075236597.squirrel@webmail.localnet.com>
2004-02-01 21:05         ` APM good, ACPI bad (2.6.2-rc1 / p4 HT / Uniwill N258SA0) Huw Rogers
2004-02-01 22:46           ` Pavel Machek
2004-02-17  2:26           ` 2.6.3-rc3-mm1 - COMPILE FAILURE Huw Rogers
2004-01-27 20:58     ` Pavel Machek [this message]

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=20040127205815.GA19011@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bart@samwel.tk \
    --cc=count0@localnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-laptop@mobilix.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

Powered by JetHome