mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: shaohua.li@intel.com, Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] swsusp: Disable nonboot CPUs before entering platform suspend
Date: Fri, 9 Mar 2007 08:11:37 +0100	[thread overview]
Message-ID: <200703090811.38559.rjw@sisk.pl> (raw)
In-Reply-To: <200703082011.15706.lenb@kernel.org>

On Friday, 9 March 2007 02:11, Len Brown wrote:
> On Wednesday 07 March 2007 18:13, Rafael J. Wysocki wrote:
> > On Wednesday, 7 March 2007 23:49, Andrew Morton wrote:
> > > On Wed, 7 Mar 2007 23:14:29 +0100
> > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > 
> > > > On Wednesday, 7 March 2007 22:16, Andrew Morton wrote:
> > > > > On Wed, 7 Mar 2007 20:44:11 +0100
> > > > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > > > 
> > > > > > From: Rafael J. Wysocki <rjw@sisk.pl>
> > > > > > 
> > > > > > Prevent the WARN_ON() in arch/x86_64/kernel/acpi/sleep.c:init_low_mapping()
> > > > > > from triggering by disabling nonboot CPUs before we finally enter the platform
> > > > > > suspend.
> > > > > > 
> > > > > > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > > > > > ---
> > > > > >  kernel/power/disk.c |    1 +
> > > > > >  kernel/power/user.c |    2 +-
> > > > > >  2 files changed, 2 insertions(+), 1 deletion(-)
> > > > > > 
> > > > > > Index: linux-2.6.21-rc2-mm2/kernel/power/disk.c
> > > > > > ===================================================================
> > > > > > --- linux-2.6.21-rc2-mm2.orig/kernel/power/disk.c
> > > > > > +++ linux-2.6.21-rc2-mm2/kernel/power/disk.c
> > > > > > @@ -61,6 +61,7 @@ static void power_down(suspend_disk_meth
> > > > > >  	switch(mode) {
> > > > > >  	case PM_DISK_PLATFORM:
> > > > > >  		if (pm_ops && pm_ops->enter) {
> > > > > > +			disable_nonboot_cpus();
> > > > > >  			kernel_shutdown_prepare(SYSTEM_SUSPEND_DISK);
> > > > > >  			pm_ops->enter(PM_SUSPEND_DISK);
> > > > > >  			break;
> > > > > > Index: linux-2.6.21-rc2-mm2/kernel/power/user.c
> > > > > > ===================================================================
> > > > > > --- linux-2.6.21-rc2-mm2.orig/kernel/power/user.c
> > > > > > +++ linux-2.6.21-rc2-mm2/kernel/power/user.c
> > > > > > @@ -398,9 +398,9 @@ static int snapshot_ioctl(struct inode *
> > > > > >  
> > > > > >  		case PMOPS_ENTER:
> > > > > >  			if (data->platform_suspend) {
> > > > > > +				disable_nonboot_cpus();
> > > > > >  				kernel_shutdown_prepare(SYSTEM_SUSPEND_DISK);
> > > > > >  				error = pm_ops->enter(PM_SUSPEND_DISK);
> > > > > > -				error = 0;
> > > > > >  			}
> > > > > >  			break;
> > > > > 
> > > > > Is this considered 2.6.21 material?  If so why?
> > > > 
> > > > Well, the WARN_ON() in arch/x86_64/kernel/acpi/sleep.c:init_low_mapping()
> > > > triggers every time an SMP x86_64 box is suspended to disk using the platform
> > > > mode (default), which is quite annoying IMHO and users think something wrong is
> > > > going on.  This will probably cause them to report the problem and I'd rather
> > > > like to avoid handling these reports. ;-)
> > > 
> > > Well sure - if patches were always error-free, we'd always apply them
> > > immediately.
> > > 
> > > The question is: is the risk of this patch breaking things exceeded by the
> > > benefit which you describe?
> > 
> > Well, it has survived some testing (http://lkml.org/lkml/2007/3/7/16).  Also,
> > before the code ordering in 2.6.21-rc* we had been running on one CPU
> > here, so I think the risk is small.
> > 
> > We could remove the WARN_ON() as Pavel has just suggested, but first I'd like
> > to know who put it there and why.
> > 
> 
> Shaohua added it between 2.6.17 and 2.6.18
> 55b2355eefc2f160246226d4d69fed431173a4d5

Yes, DaveJ has already noticed that, but what it's there for?

Rafael

      reply	other threads:[~2007-03-09  7:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 19:44 Rafael J. Wysocki
2007-03-07 21:07 ` Pavel Machek
2007-03-09  7:58   ` Rafael J. Wysocki
2007-03-09  8:54     ` Pavel Machek
2007-03-09 20:07       ` Rafael J. Wysocki
2007-03-09 21:07         ` Pavel Machek
2007-03-09 21:24           ` Rafael J. Wysocki
2007-03-09 22:13             ` Pavel Machek
2007-03-09 22:34               ` Rafael J. Wysocki
2007-03-09 22:48                 ` Pavel Machek
2007-03-09 12:29   ` Heiko Carstens
2007-03-09 19:39     ` Rafael J. Wysocki
2007-03-09 22:10     ` Pavel Machek
2007-03-07 21:16 ` Andrew Morton
2007-03-07 22:14   ` Rafael J. Wysocki
2007-03-07 22:19     ` Pavel Machek
2007-03-07 23:14       ` Rafael J. Wysocki
2007-03-07 22:49     ` Andrew Morton
2007-03-07 23:13       ` Rafael J. Wysocki
2007-03-08  0:20         ` Dave Jones
2007-03-08  0:48           ` Rafael J. Wysocki
2007-03-09  1:11         ` Len Brown
2007-03-09  7:11           ` Rafael J. Wysocki [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=200703090811.38559.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shaohua.li@intel.com \
    /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