[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1ICDNw-0008HC-00@dorka.pomaz.szeredi.hu>
Date: Sat, 21 Jul 2007 13:44:32 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: rjw@...k.pl
CC: miltonm@....com, stern@...land.harvard.edu, ying.huang@...el.com,
linux-kernel@...r.kernel.org, david@...g.hm,
linux-pm@...ts.linux-foundation.org, jbms@....edu
Subject: Re: [linux-pm] Re: Hibernation considerations
> The problem with FUSE is related to the fact that the freezer can't
> freeze uninterruptible tasks and we said that perhaps we might avoid
> it if FUSE was made freezing-aware. Still, no one has gone in this
> direction and I don't know of any plans to do that.
I thought we have fully explored this direction. Lots of emails, and
an IRC session with Pavel. Conclusion:
- It can't be done without VFS surgery + adding various hacks to fuse
- VFS surgery for the sake of a working suspend is not realistic
Although removing the freezer seems the cleanest solution, I'm not
saying the freezer can't be fixed up in the mean time.
Allowing tasks to remain in uninterruptible sleep seemed a nice way to
get around the fuse issues. What was the problem with that patch? It
was something that was supposed to have been tested in suspend2,
wasn't it?
The other one (trying to wake up task, so that may make other tasks
freezable) didn't seem such a good approach to me.
The theory is quite simple: while and after suspending devices, no
tasks must be touching said devices.
The very cleanest way to do this is in the drivers. The very simplest
way is the current freezer. But may be there are possibilities
between these two extremes.
But I can almost guarantee you, that any attempt at fixing the issues
though fuse will just result in an even bigger mess than what we
currently have.
Miklos
-
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