cpupower-set.1 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. .TH CPUPOWER\-SET "1" "22/02/2011" "" "cpupower Manual"
  2. .SH NAME
  3. cpupower\-set \- Set processor power related kernel or hardware configurations
  4. .SH SYNOPSIS
  5. .ft B
  6. .B cpupower set [ \-b VAL ] [ \-s VAL ] [ \-m VAL ]
  7. .SH DESCRIPTION
  8. \fBcpupower set \fP sets kernel configurations or directly accesses hardware
  9. registers affecting processor power saving policies.
  10. Some options are platform wide, some affect single cores. By default values
  11. are applied on all cores. How to modify single core configurations is
  12. described in the cpupower(1) manpage in the \-\-cpu option section. Whether an
  13. option affects the whole system or can be applied to individual cores is
  14. described in the Options sections.
  15. Use \fBcpupower info \fP to read out current settings and whether they are
  16. supported on the system at all.
  17. .SH Options
  18. .PP
  19. \-\-perf-bias, \-b
  20. .RS 4
  21. Sets a register on supported Intel processore which allows software to convey
  22. its policy for the relative importance of performance versus energy savings to
  23. the processor.
  24. The range of valid numbers is 0-15, where 0 is maximum
  25. performance and 15 is maximum energy efficiency.
  26. The processor uses this information in model-specific ways
  27. when it must select trade-offs between performance and
  28. energy efficiency.
  29. This policy hint does not supersede Processor Performance states
  30. (P-states) or CPU Idle power states (C-states), but allows
  31. software to have influence where it would otherwise be unable
  32. to express a preference.
  33. For example, this setting may tell the hardware how
  34. aggressively or conservatively to control frequency
  35. in the "turbo range" above the explicitly OS-controlled
  36. P-state frequency range. It may also tell the hardware
  37. how aggressively it should enter the OS requested C-states.
  38. This option can be applied to individual cores only via the \-\-cpu option,
  39. cpupower(1).
  40. Setting the performance bias value on one CPU can modify the setting on
  41. related CPUs as well (for example all CPUs on one socket), because of
  42. hardware restrictions.
  43. Use \fBcpupower -c all info -b\fP to verify.
  44. This options needs the msr kernel driver (CONFIG_X86_MSR) loaded.
  45. .RE
  46. .PP
  47. \-\-sched\-mc, \-m [ VAL ]
  48. .RE
  49. \-\-sched\-smt, \-s [ VAL ]
  50. .RS 4
  51. \-\-sched\-mc utilizes cores in one processor package/socket first before
  52. processes are scheduled to other processor packages/sockets.
  53. \-\-sched\-smt utilizes thread siblings of one processor core first before
  54. processes are scheduled to other cores.
  55. The impact on power consumption and performance (positiv or negativ) heavily
  56. depends on processor support for deep sleep states, frequency scaling and
  57. frequency boost modes and their dependencies between other thread siblings
  58. and processor cores.
  59. Taken over from kernel documentation:
  60. Adjust the kernel's multi-core scheduler support.
  61. Possible values are:
  62. .RS 2
  63. 0 - No power saving load balance (default value)
  64. 1 - Fill one thread/core/package first for long running threads
  65. 2 - Also bias task wakeups to semi-idle cpu package for power
  66. savings
  67. .RE
  68. sched_mc_power_savings is dependent upon SCHED_MC, which is
  69. itself architecture dependent.
  70. sched_smt_power_savings is dependent upon SCHED_SMT, which
  71. is itself architecture dependent.
  72. The two files are independent of each other. It is possible
  73. that one file may be present without the other.
  74. .SH "SEE ALSO"
  75. cpupower-info(1), cpupower-monitor(1), powertop(1)
  76. .PP
  77. .SH AUTHORS
  78. .nf
  79. \-\-perf\-bias parts written by Len Brown <len.brown@intel.com>
  80. Thomas Renninger <trenn@suse.de>