18c2ecf20Sopenharmony_ciToDos sorted by priority: 28c2ecf20Sopenharmony_ci 38c2ecf20Sopenharmony_ci- Use bitmask functions to parse CPU topology more robust 48c2ecf20Sopenharmony_ci (current implementation has issues on AMD) 58c2ecf20Sopenharmony_ci- Try to read out boost states and frequencies on Intel 68c2ecf20Sopenharmony_ci- Somewhere saw the ability to read power consumption of 78c2ecf20Sopenharmony_ci RAM from HW on Intel SandyBridge -> another monitor? 88c2ecf20Sopenharmony_ci- Add another c1e debug idle monitor 98c2ecf20Sopenharmony_ci -> Is by design racy with BIOS, but could be added 108c2ecf20Sopenharmony_ci with a --force option and some "be careful" messages 118c2ecf20Sopenharmony_ci- Add cpu_start()/cpu_stop() callbacks for monitor 128c2ecf20Sopenharmony_ci -> This is to move the per_cpu logic from inside the 138c2ecf20Sopenharmony_ci monitor to outside it. This can be given higher 148c2ecf20Sopenharmony_ci priority in fork_it. 158c2ecf20Sopenharmony_ci- Fork as many processes as there are CPUs in case the 168c2ecf20Sopenharmony_ci per_cpu_schedule flag is set. 178c2ecf20Sopenharmony_ci -> Bind forked process to each cpu. 188c2ecf20Sopenharmony_ci -> Execute start measures via the forked processes on 198c2ecf20Sopenharmony_ci each cpu. 208c2ecf20Sopenharmony_ci -> Run test executable in a forked process. 218c2ecf20Sopenharmony_ci -> Execute stop measures via the forked processes on 228c2ecf20Sopenharmony_ci each cpu. 238c2ecf20Sopenharmony_ci This would be ideal as it will not introduce noise in the 248c2ecf20Sopenharmony_ci tested executable. 25