ffd6a4b3f6c934f04392a53b53d5595a23b658db |
|
30-May-2013 |
Penny Chiu <pchiu@nvidia.com> |
power_HotCPUSuspend: Add NVIDIA CPUQuiet function check Add NVIDIA CPUQuiet function check. If the function is enabled, disable it before running test and restore the setting after running test. BUG=chrome-os-partner:19676 TEST=Ran test and it was passed Change-Id: I79a8381ff2001adb65a91cdee085e22d8f7d6ca2 Signed-off-by: Penny Chiu <pchiu@nvidia.com> Reviewed-on: https://gerrit.chromium.org/gerrit/57090 Reviewed-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: Michael Spang <spang@chromium.org> Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
/external/autotest/client/site_tests/power_HotCPUSuspend/power_HotCPUSuspend.py
|
0537d52c7b85e9454336449f2bc9efae5a4983a4 |
|
15-Jan-2013 |
Julius Werner <jwerner@chromium.org> |
Add power_MemorySuspend test to check for memory corruption on resume This patch adds a simple Autotest to wrap the existing memory_suspend_test tool. It also makes some cosmetic changes to the sys_power API, because I honestly don't know what I was thinking when I designed that... the method-as-a-string passing thing was horrible. Updated all current uses, that's why the CL looks so big although it is really quite harmless. CQ-DEPEND=CL:41252,CL:41251 BUG=chrome-os-partner:15654 TEST=First run all affected tests and the new power_MemorySuspend to make sure they succeed normally. Then build a kernel with the CONFIG_STRICT_DEVMEM option unset, push it to a device and run power_MemorySuspend while doing horrible things to /dev/mem in the background. Make sure that errors are detected and reported. Change-Id: I227b1785e0542c085c433d9dd04f7fe99859591c Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/41250 Reviewed-by: Michael Spang <spang@chromium.org>
/external/autotest/client/site_tests/power_HotCPUSuspend/power_HotCPUSuspend.py
|
2e6ecda978a5d086c76ca014531ea781fd3d75ae |
|
20-Dec-2012 |
Michael Spang <spang@chromium.org> |
Add "Hot CPU" suspend test This adds a test that suspend the system while at 100% CPU usage. I am not sure how useful this is, but we thought it might expose races in the suspend code that would not happen on an idle system. The race would likely need to happen before userspace is frozen. TEST=run_remote_tests.sh power_HotCPUSuspend BUG=none Change-Id: Ic4251ff4c45ee8d7c88c973a910fb035f72236e2 Reviewed-on: https://gerrit.chromium.org/gerrit/40342 Reviewed-by: Michael Spang <spang@chromium.org> Tested-by: Michael Spang <spang@chromium.org> Commit-Queue: Michael Spang <spang@chromium.org>
/external/autotest/client/site_tests/power_HotCPUSuspend/power_HotCPUSuspend.py
|