From: Oliver Neukum <oliver@neukum.name>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: question on resume()
Date: Wed, 31 Jan 2007 09:40:14 +0100 (MET) [thread overview]
Message-ID: <200701310940.26040.oliver@neukum.name> (raw)
In-Reply-To: <200701310933.29443.rjw@sisk.pl>
Am Mittwoch, 31. Januar 2007 09:33 schrieb Rafael J. Wysocki:
> On Tuesday, 30 January 2007 23:32, Rafael J. Wysocki wrote:
> > Generally, you are safe if your driver only calls wake_up() from a process
> > context, but not from .resume() or .suspend() routines (or from an
> > unfreezeable kernel thread).
>
> Ah, sorry, I've just realized I was wrong. Processes in TASK_UNINTERRUPTIBLE
> cannot be frozen! So, the above only applies to wake_up_interruptible().
So the kernel will wait for tasks in TASK_UNINTERRUPTIBLE to finish IO
before it calls suspend()? I am confused.
Regards
Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Neukum <oliver@neukum.name>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, nigel@nigel.suspend2.net,
pm list <linux-pm@lists.osdl.org>
Subject: Re: question on resume()
Date: Wed, 31 Jan 2007 09:40:14 +0100 (MET) [thread overview]
Message-ID: <200701310940.26040.oliver@neukum.name> (raw)
In-Reply-To: <200701310933.29443.rjw@sisk.pl>
Am Mittwoch, 31. Januar 2007 09:33 schrieb Rafael J. Wysocki:
> On Tuesday, 30 January 2007 23:32, Rafael J. Wysocki wrote:
> > Generally, you are safe if your driver only calls wake_up() from a process
> > context, but not from .resume() or .suspend() routines (or from an
> > unfreezeable kernel thread).
>
> Ah, sorry, I've just realized I was wrong. Processes in TASK_UNINTERRUPTIBLE
> cannot be frozen! So, the above only applies to wake_up_interruptible().
So the kernel will wait for tasks in TASK_UNINTERRUPTIBLE to finish IO
before it calls suspend()? I am confused.
Regards
Oliver
next prev parent reply other threads:[~2007-01-31 8:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 11:06 question on resume() Oliver Neukum
2007-01-29 11:24 ` Nigel Cunningham
2007-01-29 11:34 ` Oliver Neukum
2007-01-29 20:14 ` Nigel Cunningham
2007-01-29 21:04 ` Oliver Neukum
2007-01-29 21:21 ` Nigel Cunningham
2007-01-29 23:10 ` Rafael J. Wysocki
2007-01-30 16:32 ` Rafael J. Wysocki
2007-01-30 16:50 ` Oliver Neukum
2007-01-30 22:32 ` Rafael J. Wysocki
2007-01-30 22:32 ` Rafael J. Wysocki
2007-01-31 8:33 ` Rafael J. Wysocki
2007-01-31 8:33 ` Rafael J. Wysocki
2007-01-31 8:40 ` Oliver Neukum [this message]
2007-01-31 8:40 ` Oliver Neukum
2007-01-31 8:49 ` Rafael J. Wysocki
2007-01-31 9:04 ` Oliver Neukum
2007-01-31 9:04 ` Oliver Neukum
2007-01-31 9:36 ` Pavel Machek
2007-01-31 9:36 ` [linux-pm] " Pavel Machek
2007-01-31 10:14 ` Oliver Neukum
2007-01-31 10:14 ` [linux-pm] " Oliver Neukum
2007-01-31 10:30 ` Pavel Machek
2007-01-31 15:54 ` Alan Stern
2007-01-31 15:54 ` [linux-pm] " Alan Stern
2007-01-31 16:12 ` Oliver Neukum
2007-01-31 16:12 ` [linux-pm] " Oliver Neukum
2007-01-31 16:27 ` Alan Stern
2007-01-31 16:27 ` [linux-pm] " Alan Stern
2007-01-31 18:04 ` Woodruff, Richard
2007-01-31 18:04 ` [linux-pm] " Woodruff, Richard
2007-01-31 15:48 ` Alan Stern
2007-01-31 15:48 ` [linux-pm] " Alan Stern
2007-01-31 18:52 ` Rafael J. Wysocki
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=200701310940.26040.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--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.