From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@nigel.suspend2.net
Cc: Oliver Neukum <oliver@neukum.org>, linux-kernel@vger.kernel.org
Subject: Re: question on resume()
Date: Tue, 30 Jan 2007 17:32:55 +0100 [thread overview]
Message-ID: <200701301732.56444.rjw@sisk.pl> (raw)
In-Reply-To: <200701300010.38538.rjw@sisk.pl>
On Tuesday, 30 January 2007 00:10, Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 29 January 2007 22:21, Nigel Cunningham wrote:
> > Hi.
> >
> > On Mon, 2007-01-29 at 22:04 +0100, Oliver Neukum wrote:
> > > Am Montag, 29. Januar 2007 21:14 schrieb Nigel Cunningham:
> > > > Hi.
> > > >
> > > > On Mon, 2007-01-29 at 12:34 +0100, Oliver Neukum wrote:
> > > > > Am Montag, 29. Januar 2007 12:24 schrieb Nigel Cunningham:
> > > > > > Hi.
> > > > > >
> > > > > > On Mon, 2007-01-29 at 12:06 +0100, Oliver Neukum wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > may a driver call wake_up() while doing resume() ?
> > > > > >
> > > > > > I assume you mean waking a userspace process from drivers_resume(). If
> > > > > > so, the answer is no - processes will still be frozen at the point. In
> > > > > > the case of Suspend2, the LRU pages will still not have been read
> > > > > > either, so Suspend2 users would hate you for making hibernation crash
> > > > > > and burn :)
> > > > >
> > > > > If so, how do I notify tasks presumably about to be thawed that their
> > > > > IO failed?
> > > >
> > > > Do you mean I/O to disk? If so, it won't fail. All pending I/O gets
> > > > processed like normal either before or after suspending and resuming.
> > > >
> > > > If you mean something like a packet being transmitted over the network,
> > > > you should be using the normal paths for recording success/failure.
> > >
> > > I am talking about a character device that puts requests onto a queue.
> > > If the queue is restarted after resumption the normal error path is waking
> > > up the waiting tasks.
> >
> > Ok. In that case, you'd want to delay trying to wake them until resuming
> > is completed.
> >
> > Unless there's something I've forgotten, we don't currently have an easy
> > way for you to determine when processes are thawed.
>
> That's correct.
However, you can always inspect the PF_FROZEN flag of the tasks in question
if that's practicable.
So, while we do not have a mechanism for checking if all tasks have been
thawed, we can do it on a per-task basis quite easily.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
next prev parent reply other threads:[~2007-01-30 16:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 11:06 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 [this message]
2007-01-30 16:50 ` Oliver Neukum
2007-01-30 22:32 ` Rafael J. Wysocki
2007-01-31 8:33 ` Rafael J. Wysocki
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:36 ` [linux-pm] " Pavel Machek
2007-01-31 10:14 ` Oliver Neukum
2007-01-31 10:30 ` Pavel Machek
2007-01-31 15:54 ` Alan Stern
2007-01-31 16:12 ` Oliver Neukum
2007-01-31 16:27 ` Alan Stern
2007-01-31 18:04 ` Woodruff, Richard
2007-01-31 15:48 ` 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=200701301732.56444.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=oliver@neukum.org \
/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