public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: broken suspend (sched related) [Was: 2.6.24-rc4-mm1]
Date: Mon, 10 Dec 2007 10:10:52 +0100	[thread overview]
Message-ID: <20071210091052.GA14487@elte.hu> (raw)
In-Reply-To: <475CFF01.2090502@gmail.com>


> > softlockup: remove get_online_cpus() which doesn't help here.
> > 
> > The get_online_cpus() protection seems to be bogus in 
> > kernel/softlockup.c as cpu cached in check_cpu can go offline once 
> > we do a put_online_cpus().
> > 
> > This can also cause deadlock during a cpu offline as follows:

i'm wondering, what's the proper CPU-hotplug safe sequence here then? 
I'm picking a CPU number from cpu_online_map, and that CPU could go away 
while i'm still using it, right? What's saving us here?

	Ingo

  parent reply	other threads:[~2007-12-10  9:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071204211701.994dfce6.akpm@linux-foundation.org>
2007-12-07 14:34 ` broken suspend (sched related) [Was: 2.6.24-rc4-mm1] Jiri Slaby
2007-12-07 15:11   ` Ingo Molnar
     [not found]   ` <20071207151150.GB24254@elte.hu>
2007-12-07 17:51     ` Ingo Molnar
2007-12-08  8:10       ` Jiri Slaby
     [not found]       ` <475A5188.6070809@gmail.com>
2007-12-08  8:39         ` Ingo Molnar
     [not found]         ` <20071208083939.GD30997@elte.hu>
2007-12-08  9:23           ` Jiri Slaby
     [not found]           ` <475A629C.7010408@gmail.com>
2007-12-08 15:24             ` Ingo Molnar
2007-12-08 17:34               ` Jiri Slaby
2007-12-08 17:43               ` Jiri Slaby
2007-12-08 23:12               ` Jiri Slaby
     [not found]               ` <475B24F4.3090904@gmail.com>
2007-12-09  7:46                 ` Ingo Molnar
     [not found]                 ` <20071209074647.GE22981@elte.hu>
2007-12-09  9:09                   ` Jiri Slaby
2007-12-10  8:19                   ` Gautham R Shenoy
2007-12-10  8:55                     ` Jiri Slaby
     [not found]                     ` <475CFF01.2090502@gmail.com>
2007-12-10  9:10                       ` Ingo Molnar [this message]
2007-12-10 10:15                         ` Gautham R Shenoy
     [not found]                         ` <20071210101500.GB12880@in.ibm.com>
2007-12-10 10:21                           ` Ingo Molnar
     [not found]                           ` <20071210102157.GB31103@elte.hu>
2007-12-10 11:08                             ` Gautham R Shenoy
2007-12-10 11:28                               ` Ingo Molnar
     [not found]                               ` <20071210112832.GA20189@elte.hu>
2007-12-10 11:49                                 ` Gautham R Shenoy
2007-12-10  9:29                     ` Ingo Molnar
     [not found]               ` <475AD7D0.8040905@gmail.com>
2007-12-09  8:06                 ` Ingo Molnar

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=20071210091052.GA14487@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=tglx@linutronix.de \
    /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