Hi! > >> Power management debug option to configure device suspend/resume watchdogs. > >> Available options are: > >> 1. Enable/disable the feature. > >> 2. Select triggered watchdog action between: > >> - system panic (default) > >> - dump stacktrace > >> - log event > >> 3. Select timeout value for the watchdog(s). > > > > People disliked the previous behaviour, so you add 10 config > > options... with different behaviours. Also 1 second timeout is not > > acceptable for endusers (will break the system), so it should not be > > offered. In fact, remove that option, too. People doing that kind of > > debugging can modify the sources, right? > > Greg KH asked for more configurable options. I agree this may be a > little too far (I would replace the action choice with a simple "panic > on timeout?"), but its better than it was before. Also, a 1 second > timeout is perfectly reasonable, especially if you configure it to > dump a stack trace but not panic. Mobile devices normally finish > suspending within a few hundred ms.
For stack dump, yes that's ok. Maybe it ends up less ugly if it will be runtime-configurable? -- (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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/