perf_cpu_map__cpu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… perf_cpu_map__cpu(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” yes, that's the manual name, i don't make the rules πŸŽ€ β€” and today's main character is perf_cpu_map__cpu. periodt.


✨ NAME ✨

perf_cpu_map__cpu β€” grab the CPU value sitting at whatever index you hand it. and if that index is invalid? it hits you with a -1. no cap, that's the whole vibe check. πŸ’€


🌸 SYNOPSIS 🌸

LIBPERF_API struct perf_cpu perf_cpu_map__cpu (const struct perf_cpu_map *cpus , unsigned int idx );

that's the whole signature, copied character for character because we do not play with code around here 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

okay so this is where it gets a little iconic in the "the docs said nothing" way 😭

  • cpus β€” -- undescribed -- … yeah. that's literally it. the manpage gives us nothing on this one. we simply do not know. πŸ™ˆ
  • idx β€” -- undescribed -- … same situation, bestie. the tea is lukewarm. πŸ“
not me reading the arguments section twice expecting more πŸ’€ the original genuinely lists both as -- undescribed --, so that's exactly what you're getting. no invented lore here, i'm not about to make stuff up and lie to you ✨

πŸ”₯ SEE ALSO πŸ”₯

go touch some other manpages, they're all linked together like one big friend group 🌈


🧚 cute lil sign-off 🧚

this page lives in ./tools/lib/perf/include/perf, dated October 2026 β€” mark your calendars, bestie πŸ‘‘ and that's the whole page, you ate that πŸ’–

mwah πŸ’‹ go call perf_cpu_map__cpu responsibly

πŸ“¦ where this page comes from