perf_cpu_ma..._or_is_empty(9)

💅 NAME 💅

perf_cpu_map__has_any_cpu_or_is_empty — bestie, this one asks the real questions: is this map either empty, or does it have that "any CPU"/dummy value? That's it, that's the whole vibe check 🔥

This page lives in the Kernel API Manual, and the title got cut off at perf_cpu_ma..._or_is_empty(9) so like… yeah, we're working with what we've got 🫶

---

✨ SYNOPSIS ✨

okay so here's the exact signature, no cap, copy it verbatim:

LIBPERF_API bool perf_cpu_map__has_any_cpu_or_is_empty (const struct
perf_cpu_map *map );

notice the LIBPERF_API prefix, the bool return, and the const struct perf_cpu_map *map — all of it, literally character for character 👑

---

🎀 ARGUMENTS 🎀

• map — so the manpage itself just says -- undescribed -- for this one 😭 like the docs literally gave us nothing. It's a const struct perf_cpu_map *map, that's what the synopsis says, and the description is… not written. Not me being lazy, the source is just built different (derogatory). If you need to know more about it, that's a cpumap.h girlie's job 🙈

---

🦋 SEE ALSO 🦋

the whole friend group, in order 💖 and yes the first one is a kernel file path:

• Kernel file ./tools/lib/perf/include/perf/cpumap.h
• struct perf_cpu(9)
• perf_cpu_map__new_any_cpu(9)
• perf_cpu_map__new_online_cpus(9)
• perf_cpu_map__new(9)
• perf_cpu_map__cpu(9)
• perf_cpu_map__nr(9)
• perf_cpu_map__is_any_cpu_or_is_empty(9)
• perf_cpu_map__is_empty(9)
• perf_cpu_map__min(9)
• perf_cpu_map__max(9)

go read them, they ate 💅

---

so yeah, that's the page 🌸 it's short, it's sweet, the argument section is a mystery, and honestly? iconic for that.

sign-off time 🎀 this beauty comes from ./tools/lib/perf/include/perf, dated October 2026, and the page answers to perf_cpu_ma..._or_is_empty(9) — yes, still truncated, we stan a consistent queen ✨💜