~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/tools/power/cpupower/TODO

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /tools/power/cpupower/TODO (Architecture i386) and /tools/power/cpupower/TODO (Architecture alpha)


  1 ToDos sorted by priority:                           1 ToDos sorted by priority:
  2                                                     2 
  3 - Use bitmask functions to parse CPU topology       3 - Use bitmask functions to parse CPU topology more robust
  4   (current implementation has issues on AMD)        4   (current implementation has issues on AMD)
  5 - Try to read out boost states and frequencies      5 - Try to read out boost states and frequencies on Intel
  6 - Somewhere saw the ability to read power cons      6 - Somewhere saw the ability to read power consumption of
  7   RAM from HW on Intel SandyBridge -> another       7   RAM from HW on Intel SandyBridge -> another monitor?
  8 - Add another c1e debug idle monitor                8 - Add another c1e debug idle monitor
  9   -> Is by design racy with BIOS, but could be      9   -> Is by design racy with BIOS, but could be added
 10      with a --force option and some "be carefu     10      with a --force option and some "be careful" messages
 11 - Add cpu_start()/cpu_stop() callbacks for mon     11 - Add cpu_start()/cpu_stop() callbacks for monitor
 12   -> This is to move the per_cpu logic from in     12   -> This is to move the per_cpu logic from inside the
 13      monitor to outside it. This can be given      13      monitor to outside it. This can be given higher
 14      priority in fork_it.                          14      priority in fork_it.
 15 - Fork as many processes as there are CPUs in      15 - Fork as many processes as there are CPUs in case the
 16   per_cpu_schedule flag is set.                    16   per_cpu_schedule flag is set.
 17   -> Bind forked process to each cpu.              17   -> Bind forked process to each cpu.
 18   -> Execute start measures via the forked pro     18   -> Execute start measures via the forked processes on
 19      each cpu.                                     19      each cpu.
 20   -> Run test executable in a forked process.      20   -> Run test executable in a forked process.
 21   -> Execute stop measures via the forked proc     21   -> Execute stop measures via the forked processes on
 22      each cpu.                                     22      each cpu.
 23   This would be ideal as it will not introduce     23   This would be ideal as it will not introduce noise in the
 24   tested executable.                               24   tested executable.
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php