From: Oleg Nesterov <oleg@tv-sign.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Alex Dubov <oakad@yahoo.com>, Pierre Ossman <drzeus@drzeus.cx>
Subject: Re: 2.6.22-rc1: Broken suspend on SMP with tifm
Date: Mon, 14 May 2007 00:08:45 +0400 [thread overview]
Message-ID: <20070513200845.GA3078@tv-sign.ru> (raw)
In-Reply-To: <200705132132.08546.rjw@sisk.pl>
On 05/13, Rafael J. Wysocki wrote:
>
> The suspend/hibernation is broken on SMP due to:
>
> commit 3540af8ffddcdbc7573451ac0b5cd57a2eaf8af5
> tifm: replace per-adapter kthread with freezeable workqueue
>
> Well, it looks like freezable worqueues still deadlock with CPU hotplug
> when worker threads are frozen.
Ugh. I thought we deprecated create_freezeable_workqueue(), exactly
because suspend was changed to call _cpu_down() after freeze().
It is not that "looks like freezable worqueues still deadlock", it
is "of course, freezable worqueues deadlocks" on CPU_DEAD.
The ->freezeable is still here just because of incoming "cpu-hotplug
using freezer" rework.
No?
> --- linux-2.6.22-rc1.orig/kernel/workqueue.c
> +++ linux-2.6.22-rc1/kernel/workqueue.c
> @@ -799,9 +799,7 @@ static int __devinit workqueue_cpu_callb
> struct cpu_workqueue_struct *cwq;
> struct workqueue_struct *wq;
>
> - action &= ~CPU_TASKS_FROZEN;
> -
> - switch (action) {
> + switch (action & ~CPU_TASKS_FROZEN) {
Confused. How can we see, say CPU_UP_PREPARE_FROZEN, if we cleared
CPU_TASKS_FROZEN bit?
> case CPU_LOCK_ACQUIRE:
> mutex_lock(&workqueue_mutex);
> return NOTIFY_OK;
> @@ -819,20 +817,29 @@ static int __devinit workqueue_cpu_callb
>
> switch (action) {
> case CPU_UP_PREPARE:
> + case CPU_UP_PREPARE_FROZEN:
> if (!create_workqueue_thread(cwq, cpu))
> break;
> printk(KERN_ERR "workqueue for %i failed\n", cpu);
> return NOTIFY_BAD;
>
> case CPU_ONLINE:
> + case CPU_ONLINE_FROZEN:
> start_workqueue_thread(cwq, cpu);
> break;
>
> case CPU_UP_CANCELED:
> + case CPU_UP_CANCELED_FROZEN:
> start_workqueue_thread(cwq, -1);
> case CPU_DEAD:
> cleanup_workqueue_thread(cwq, cpu);
> break;
> +
> + case CPU_DEAD_FROZEN:
> + if (wq->freezeable)
> + thaw_process(cwq->thread);
> + cleanup_workqueue_thread(cwq, cpu);
> + break;
> }
> }
Minor, but can't we do
...
case CPU_UP_CANCELED:
case CPU_UP_CANCELED_FROZEN:
start_workqueue_thread(cwq, -1);
case CPU_DEAD_FROZEN:
if (wq->freezeable)
// we can't see PF_FROZEN if it was CPU_UP_CANCELED
thaw_process(cwq->thread);
case CPU_DEAD:
cleanup_workqueue_thread(cwq, cpu);
break;
?
Oleg.
next prev parent reply other threads:[~2007-05-13 20:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 19:32 2.6.22-rc1: Broken suspend on SMP with tifm Rafael J. Wysocki
2007-05-13 20:08 ` Oleg Nesterov [this message]
2007-05-13 20:30 ` Oleg Nesterov
2007-05-13 20:50 ` Rafael J. Wysocki
2007-05-13 20:50 ` Oleg Nesterov
2007-05-13 21:22 ` Rafael J. Wysocki
2007-05-13 21:34 ` Oleg Nesterov
2007-05-13 21:50 ` Rafael J. Wysocki
2007-05-13 21:54 ` Oleg Nesterov
2007-05-13 22:21 ` Rafael J. Wysocki
2007-05-13 22:32 ` Oleg Nesterov
2007-05-14 3:24 ` Alex Dubov
2007-05-14 5:57 ` Rafael J. Wysocki
2007-05-14 16:55 ` Freezeable workqueues [Was: 2.6.22-rc1: Broken suspend on SMP with tifm] Oleg Nesterov
2007-05-14 21:27 ` Rafael J. Wysocki
2007-05-14 21:48 ` Oleg Nesterov
2007-05-15 0:56 ` Alex Dubov
2007-05-15 20:54 ` Rafael J. Wysocki
2007-05-15 20:54 ` Rafael J. Wysocki
2007-05-20 19:54 ` Oleg Nesterov
2007-05-20 20:48 ` Rafael J. Wysocki
2007-05-20 21:06 ` Oleg Nesterov
2007-05-20 21:49 ` Rafael J. Wysocki
2007-05-13 20:33 ` 2.6.22-rc1: Broken suspend on SMP with tifm Rafael J. Wysocki
2007-05-13 21:52 ` [PATCH] for 2.6.22, make freezeable workqueues singlethread Oleg Nesterov
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=20070513200845.GA3078@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=oakad@yahoo.com \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.