aggr_cpu_id__socket(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… aggr_cpu_id__socket(9) β€” the kernel API manual, but make it make sense

okay so bestie, welcome to aggr_cpu_id__socket, straight out of the kernel API manual (section 9, kernel developer girly territory ✨). This one's a tiny little function with main character energy β€” it builds you an aggr_cpu_id with the socket field already filled in from the cpu you hand it. Iconic, low effort, high payoff. πŸŽ€


🌸 NAME

aggr_cpu_id__socket β€” create an aggr_cpu_id with the socket populated with the socket for cpu. The function signature is compatible with aggr_cpu_id_get_t. no cap, that's literally the whole job 🫢


✨ SYNOPSIS

struct aggr_cpu_id aggr_cpu_id__socket (struct perf_cpu cpu , void *data );

that's it. that's the whole vibe check. πŸ¦‹


🧚 ARGUMENTS

  • cpu β€” -- undescribed -- πŸ™ˆ the manual literally gives us nothing here, so we're not gonna invent lore. It's a struct perf_cpu, it's your cpu, it goes in.
  • data β€” -- undescribed -- πŸ’€ also undescribed, also a void *, also just vibing. We do not speculate. We do not make things up. Periodt.

πŸ”₯ SEE ALSO

the whole friend group, assembled 🌈 β€” all these live in the kernel file ./tools/perf/util/cpumap.h:

like, the full aggr_cpu_id cinematic universe πŸ‘‘ iykyk.


quick reminder bestie: cpu and data are both marked -- undescribed -- in the original β€” no guessing, no fanfic, no "well actually I think it does…". we keep it honest. πŸ’œ

and that's the page! πŸ“ brought to you by the source at ./tools/perf/util, dated October 2026 β€” mwah, sending you a little πŸ’– from the kernel tree. slay safe out there! ✨

πŸ“¦ where this page comes from