Hi!
> Introduce /sys/power/pm_test_level attribute allowing one to test the suspend
> core code. Namely, writing a number (1-5) to this file causes the suspend
> code
> to work in one of the test modes defined as follows:
>
> 5 - test the freezing of processes
> 4 - test the freezing of processes and suspending of devices
> 3 - test the freezing of processes, suspending of devices and platform global
> control methods
> 2 - test the freezing of processes, suspending of devices, platform global
> control methods and the disabling of nonboot CPUs
> 1 - test the freezing of processes, suspending of devices, platform global
> control methods, the disabling of nonboot CPUs and suspending of
> platform/system devices
>
> Then, if a suspend is started by normal means, the suspend core will perform
> its normal operations up to the point indicated by the test level. Next, it
> will wait for 5 seconds and carry out the resume operations needed to
> transition
> the system back to the fully functional state.
>
> Writing 0 to /sys/power/pm_test_level turns the testing off. The current test
> level may be read from /sys/power/pm_test_level .
>
> Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>
ACK on whole series, but... should we also remove the old debugging
infrastructure? (Or did I just miss it?)
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
