4611a4fb0c
Based on Thomas Renninger's feedback/ideas. Re-structure the code to better handle the per_cpu_schedule mechanism which was introduced when adding support for AMD Zen based processors. Signed-off-by: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com> Acked-by: Thomas Renninger <trenn@suse.de> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
25 lines
1.0 KiB
Plaintext
25 lines
1.0 KiB
Plaintext
ToDos sorted by priority:
|
|
|
|
- Use bitmask functions to parse CPU topology more robust
|
|
(current implementation has issues on AMD)
|
|
- Try to read out boost states and frequencies on Intel
|
|
- Somewhere saw the ability to read power consumption of
|
|
RAM from HW on Intel SandyBridge -> another monitor?
|
|
- Add another c1e debug idle monitor
|
|
-> Is by design racy with BIOS, but could be added
|
|
with a --force option and some "be careful" messages
|
|
- Add cpu_start()/cpu_stop() callbacks for monitor
|
|
-> This is to move the per_cpu logic from inside the
|
|
monitor to outside it. This can be given higher
|
|
priority in fork_it.
|
|
- Fork as many processes as there are CPUs in case the
|
|
per_cpu_schedule flag is set.
|
|
-> Bind forked process to each cpu.
|
|
-> Execute start measures via the forked processes on
|
|
each cpu.
|
|
-> Run test executable in a forked process.
|
|
-> Execute stop measures via the forked processes on
|
|
each cpu.
|
|
This would be ideal as it will not introduce noise in the
|
|
tested executable.
|