cpufreq-info(1)

πŸ“¦
version 008 Β· 2 versions
, in debian bookworm, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’– cpufreq-info β€” the manual page, but make it cute πŸ’–

okay so bestie, welcome to cpufreq-info(1), section 1 of the manual, the one and only ✨


🌸 NAME 🌸

cpufreq-info β€” the little utility that goes and retrieves your cpufreq kernel information, no cap πŸ’…


πŸŽ€ SYNTAX πŸŽ€

cpufreq-info [options]

that's it. that's the whole vibe. just the command and whatever options you're feeling 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

it's a small tool, right? tiny. humble. but what it does is it prints out cpufreq information, and it's literally so helpful β€” for developers, and for interested users like you and me πŸ’–

like it's giving "quietly carrying the whole team" energy. main character behavior, honestly. πŸ‘‘


⭐ OPTIONS ⭐

here's where it gets iconic. every flag, every letter, all of it:

  • -c, --cpu <CPU> β€” pick the <CPU> number you want the info about. that's the one she'll investigate πŸ”
  • -e, --debug β€” prints out debug information. for when you wanna see everything πŸ›
  • -f, --freq β€” gets the frequency the CPU is currently running at, according to the cpufreq core 🌑️
  • -w, --hwfreq β€” gets the frequency the CPU is currently running at, but by reading it straight from the hardware. heads up bestie: this one's only available to root πŸ”
  • -l, --hwlimits β€” figures out the minimum and maximum CPU frequency allowed. the whole range, the whole spectrum 🌈
  • -d, --driver β€” determines the cpufreq kernel driver that's being used πŸš—
  • -p, --policy β€” gets the currently used cpufreq policy πŸ“œ
  • -g, --governors β€” determines which cpufreq governors are available πŸ‘‘
  • -a, --related-cpus β€” determines which CPUs run at the same hardware frequency πŸ‘―
  • -a, --affected-cpus β€” determines which CPUs need to have their frequency coordinated by software 🧠
  • -s, --stats β€” shows cpufreq statistics, if available πŸ“Š
  • -y, --latency β€” determines the maximum latency on CPU frequency changes ⏱️
  • -o, --proc β€” prints out information like the stuff provided by the /proc/cpufreq interface back in 2.4. and early 2.6. kernels. vintage, honestly πŸ•°οΈ
  • -m, --human β€” human-readable output for the -f, -w, -s and -y parameters. like, finally, words a person can read 🫢
  • -h, --help β€” prints out the help screen. the classic. the legend πŸ“–

πŸ’€ REMARKS πŸ’€

okay so there are rules, and you will respect them:

you can't specify more than one of the output specific options: -o -e -a -g -p -d -l -w -f -y.

one at a time, bestie. she's not a multitasker. pick a lane πŸ’…

you also can't specify the -o option combined with the -c option.

just. don't. it's not a thing. the tool said no and we respect the tool πŸ™ˆ


πŸ“ FILES πŸ“

where the magic lives:

  • /sys/devices/system/cpu/cpu*/cpufreq/
  • /proc/cpufreq (deprecated)
  • /proc/sys/cpu/ (deprecated)
lowkey a warning: those last two are marked deprecated in the original, so don't go building your whole personality around them 🧚

🌟 AUTHORS 🌟

  • Dominik Brodowski <linux@brodo.de> β€” author πŸ’œ
  • Mattia Dongili <malattia@gmail.com> β€” first autolibtoolization πŸ› οΈ

πŸ”₯ SEE ALSO πŸ”₯

go read those next, iykyk πŸ“š


and that's the page, bestie πŸŽ€ this one came from Mattia Dongili, version 0.1, and it's the cpufreq-info(1) manual β€” periodt. go forth and interrogate your CPU πŸ’–βœ¨

πŸ“¦ where this page comes from