25 lines · plain
1ToDos sorted by priority:2 3- Use bitmask functions to parse CPU topology more robust4 (current implementation has issues on AMD)5- Try to read out boost states and frequencies on Intel6- Somewhere saw the ability to read power consumption of7 RAM from HW on Intel SandyBridge -> another monitor?8- Add another c1e debug idle monitor9 -> Is by design racy with BIOS, but could be added10 with a --force option and some "be careful" messages11- Add cpu_start()/cpu_stop() callbacks for monitor12 -> This is to move the per_cpu logic from inside the13 monitor to outside it. This can be given higher14 priority in fork_it.15- Fork as many processes as there are CPUs in case the16 per_cpu_schedule flag is set.17 -> Bind forked process to each cpu.18 -> Execute start measures via the forked processes on19 each cpu.20 -> Run test executable in a forked process.21 -> Execute stop measures via the forked processes on22 each cpu.23 This would be ideal as it will not introduce noise in the24 tested executable.25