[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070712151308.GA5139@ucw.cz>
Date: Thu, 12 Jul 2007 15:13:08 +0000
From: Pavel Machek <pavel@....cz>
To: Paul Mackerras <paulus@...ba.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Oliver Neukum <oliver@...kum.org>,
Miklos Szeredi <miklos@...redi.hu>, mjg59@...f.ucam.org,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway
Hi!
> > They will not trigger 100% of the time, but sporadically and generally at
> > random.
> >
> > At least the freezer problems are reproducible. ;-)
>
> Our experience with powermacs has been that it isn't actually all that
> hard to get it right for the drivers you care about.
So... will you fix input and usb? Their maintainers seem to prefer
simplicity of frozen system.
Also, can you write down rules for drivers to follow?
Like... 'if you get a request after system suspend started, you may
not kmalloc(GFP_KERNEL)'
- because disk driver may be already suspended
- hmm, what happens if disk driver _is_ suspended? Let's say I'm v4l
driver on cpu1. Someone may talk to me _while_ disk driver is being
suspended... and if I'm after disk driver in pci order, I may only
learn about suspend _after_ I do the wrong kmalloc.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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