aboutsummaryrefslogtreecommitdiffstats
path: root/tools/power/cpupower/ToDo
diff options
context:
space:
mode:
authorozkanonur <onurozkan.dev@gmail.com>2022-01-13 00:04:21 +0300
committerShuah Khan <skhan@linuxfoundation.org>2022-01-24 09:07:11 -0700
commit101025ff8e47d3c938ad2ae646a1794b9a8aa730 (patch)
treeefcf24bb0c4578d6ac7474b0146e9a22cdf290bb /tools/power/cpupower/ToDo
parenttools: cpupower: fix typo in cpupower-idle-set(1) manpage (diff)
downloadlinux-dev-101025ff8e47d3c938ad2ae646a1794b9a8aa730.tar.xz
linux-dev-101025ff8e47d3c938ad2ae646a1794b9a8aa730.zip
tools/power/cpupower/{ToDo => TODO}: Rename the todo file
Renamed the to-do file to 'TODO' instead of 'ToDo' to comply with the naming standard. Signed-off-by: ozkanonur <onurozkan.dev@gmail.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/power/cpupower/ToDo')
-rw-r--r--tools/power/cpupower/ToDo24
1 files changed, 0 insertions, 24 deletions
diff --git a/tools/power/cpupower/ToDo b/tools/power/cpupower/ToDo
deleted file mode 100644
index b196a139a3e4..000000000000
--- a/tools/power/cpupower/ToDo
+++ /dev/null
@@ -1,24 +0,0 @@
-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.