[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200701292204.33112.oliver@neukum.org>
Date: Mon, 29 Jan 2007 22:04:32 +0100
From: Oliver Neukum <oliver@...kum.org>
To: nigel@...el.suspend2.net
Cc: linux-kernel@...r.kernel.org
Subject: Re: question on resume()
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.
Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists