[lkml]   [2017]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line
>> > Oh - and talking about "big step forward" - does the 0day robot do
>> > any
>> > suspend/resume testing at all?
>> Yes, we do. CC Rui and Aaron on power testing.
>yes, we have added suspend/resume test in 0day, including both
>functionality and suspend/resume performance. It is not widely run
>because most of the 0Day testboxes are servers/desktops, now we've just
>added some client laptops as testboxes, and will add more in the near
>future. :)
>> >
>> > Even on non-laptop hardware, it should be possible to do something
>> > like
>> >
>> >    echo platform > /sys/power/pm_test
>> >    echo freeze > /sys/power/state
>> >
>> > or similar (assuming CONFIG_PM_DEBUG is enabled).
>> >
>I will run native suspend/resume test on laptops and other test boxes
>that really support it, and run suspend/resume test in pm_test modes on
>the others to help us find more issues.

It's a good plan, thanks! Client devices can be much cheaper than servers.
They have more diversities in HW while being more general available.

On the other hand, if there are PM functionalities that can be tested
inside QEMU, it'll be good to have. Since no real HW can be tested as
cheap and extensive as the large amount of VMs.


 \ /
  Last update: 2017-11-13 03:22    [W:0.115 / U:2.952 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site