public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: suspend-devel List <suspend-devel@lists.sourceforge.net>,
	seife@suse.de, pm list <linux-pm@lists.osdl.org>
Subject: Re: [RFC][PATCH -mm] PM: Change ordering of suspend and resume code
Date: Sun, 26 Nov 2006 11:08:30 +0100	[thread overview]
Message-ID: <200611261108.30532.rjw@sisk.pl> (raw)
In-Reply-To: <20061126074400.GA12479@elf.ucw.cz>

Hi,

On Sunday, 26 November 2006 08:44, Pavel Machek wrote:
> Hi!
> 
> > The discussion in a recent thread on Linux-PM has indicated that it's
> > necessary to call pm_ops->finish() before devce_resume(),
> > but enable_nonboot_cpus() has to be called before pm_ops->finish()
> > (cf. http://lists.osdl.org/pipermail/linux-pm/2006-November/004164.html).
> > For consistency, it seems reasonable to call disable_nonboot_cpus() after
> > device_suspend().
> > 
> > This way the suspend code will remain symmetrical with respect to the resume
> > code and it may allow us to speed up things in the future by suspending and
> > resuming devices and/or saving the suspend image in many threads, but for this
> > purpose we first need to make freeze_processes() SMP-safe.
> 
> I do not think first patch is enough to make it SMP-safe, sorry.

So, what is the scenario in which it will fail?

> > The following series of patches makes freeze_processes() SMP-safe and
> > reorders the suspend and resume code so that nonboot CPUs are disabled
> > after devices have been suspended and enabled before the devices are
> > resumed.  It also causes pm_ops->finish() to be called after
> > enable_nonboot_cpus() wherever necessary.
> > 
> > The first four patches have been tested on two different x86-64 SMP boxes and
> > they don't seem to break anything.  Still, if anyone can test them on some other
> > SMP boxes (especially on i386 ones), please do so and tell me if there are
> > any problems.
> > 
> > The last patch is untested.
> 
> I guess I should fix s2ram enough that it works for you... What is the
> primary notebook you are using?

HPC nx6325.  Someone has reported he's managed to get s2ram working on it,
but it looks like his machine is slightly different to this one ...

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-11-26 10:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-25 21:10 [RFC][PATCH -mm] PM: Change ordering of suspend and resume code Rafael J. Wysocki
2006-11-25 21:29 ` [RFC][PATCH -mm 1/5] PM: Make freeze_processes SMP-safe Rafael J. Wysocki
2006-11-26  7:47   ` Pavel Machek
2006-11-26 10:02     ` Rafael J. Wysocki
2006-11-26 11:15       ` Rafael J. Wysocki
2006-11-26 13:34         ` Rafael J. Wysocki
2006-11-26 19:48           ` Pavel Machek
2006-11-26 23:09             ` Rafael J. Wysocki
2006-11-26 23:28               ` Pavel Machek
2006-11-27  2:41                 ` [linux-pm] " Alan Stern
2006-11-27 20:04                 ` Rafael J. Wysocki
2006-11-27 10:50               ` Pavel Machek
2006-11-27 20:02                 ` Rafael J. Wysocki
2006-11-29 23:56                   ` Pavel Machek
2006-11-28 23:40               ` Rafael J. Wysocki
2006-11-29 23:55                 ` Pavel Machek
2006-11-30  0:21                   ` Rafael J. Wysocki
2006-11-30 15:07                     ` Rafael J. Wysocki
2006-11-30 15:43                       ` [linux-pm] " Alan Stern
2006-11-30 16:04                         ` Rafael J. Wysocki
2006-11-30 19:23                           ` Rafael J. Wysocki
2006-11-30 22:34                             ` Alan Stern
2006-11-30 22:57                               ` Rafael J. Wysocki
2006-12-01 14:56                                 ` Alan Stern
2006-12-01 19:57                                   ` Rafael J. Wysocki
2006-12-01 21:17                                     ` Alan Stern
2006-12-01 21:19                                       ` Rafael J. Wysocki
2006-12-01 22:07                                         ` Alan Stern
2006-12-01 23:38                                           ` Rafael J. Wysocki
2006-12-02 11:55                                       ` Pavel Machek
2006-12-02 15:39                                         ` Alan Stern
2006-12-03 11:17                                           ` Rafael J. Wysocki
2006-11-30 21:55                       ` [Suspend-devel] " Rafael J. Wysocki
2006-11-26 19:45         ` [linux-pm] " Pavel Machek
2006-11-26 23:37     ` Luca
2006-11-25 21:34 ` [RFC][PATCH -mm 2/5] swsusp: Change code ordering in disk.c Rafael J. Wysocki
2006-11-25 21:38 ` [RFC][PATCH -mm 3/5] swsusp: Change code ordering in user.c Rafael J. Wysocki
2006-11-25 21:45 ` [RFC][PATCH -mm 4/5] swsusp: Add PLATFORM_SNAPSHOT and PLATFORM_RESTORE ioctls Rafael J. Wysocki
2006-11-26 19:51   ` [linux-pm] " Pavel Machek
2006-11-26 23:12     ` Rafael J. Wysocki
2006-11-26 23:29       ` Pavel Machek
2006-11-27 10:37         ` Pavel Machek
2006-11-25 21:49 ` [RFC][PATCH -mm 5/5] PM: Change code ordering in main.c Rafael J. Wysocki
2006-11-26  7:44 ` [RFC][PATCH -mm] PM: Change ordering of suspend and resume code Pavel Machek
2006-11-26 10:08   ` Rafael J. Wysocki [this message]
2006-11-26 21:31     ` Pavel Machek
2006-11-26 23:15       ` Rafael J. Wysocki
2006-11-30 14:02       ` Stefan Seyfried

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=200611261108.30532.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    --cc=seife@suse.de \
    --cc=suspend-devel@lists.sourceforge.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