Warren Block <[email protected]> wrote: > On Sun, 4 May 2014, Adrian Chadd wrote:
> > The easy-to-run test is "sysctl dev.cpu.0.cx_lowest=Cmax" and then use > > stuff. > > It's that "use stuff" step that would preferably be automated. Is the > failure mode a lockup, or could a program detect problems? The idea > is to get lots of feedback, fast. One possible failure mode is that timers tick unreliably which can be detected automatically (in some cases), for example by using the DTrace script timestamp-test.d: http://www.fabiankeil.de/gehacktes/dtrace-timestamp-tests/ It should also be possible to let the kernel do this itself and log an error message and maybe optionally disable Cx states that cause problems: sysctl dev.cpu.0.cx_lowest=Cmax-as-long-as-it-appears-to-be-working Fabian
signature.asc
Description: PGP signature
