acpi_get_cache_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_get_cache_info β€” Kernel API Manual, section 9, bestie

okay so picture this: it's a (9) manpage, it lives in the Kernel API Manual, and its whole personality is "tell me about the caches on this PE." iconic behavior honestly.


✨ NAME ✨

acpi_get_cache_info β€” determine the number of cache levels and split cache levels (data/instruction) and for a PE. πŸŽ€

πŸ¦‹ SYNOPSIS πŸ¦‹

int acpi_get_cache_info (unsigned int cpu , unsigned int *levels ,
       unsigned int *split_levels );

🌸 ARGUMENTS 🌸

  • cpu β€” the kernel logical CPU number. like, which CPU are we talking about, bestie? πŸ‘€
  • levels β€” number of levels if success. ✨
  • split_levels β€” number of levels being split (i.e. data/instruction) if success. and get this, it can by NULL β€” yes, that's the manpage's wording, no cap, we do not touch it πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

Given a logical CPU number, this returns the number of levels of cache represented in the PPTT. that's the whole vibe. 🧚

but listen β€” errors caused by lack of a PPTT table, or otherwise, return 0, indicating we didn't find any cache levels. so a 0 here is giving "nothing to see here" energy, not "slay." πŸ’€

πŸ”₯ RETURN πŸ”₯

  • -ENOENT if no PPTT table, can't get CPU's ACPI Process UID or no PPTT processor struct found. 😭
  • 0 on success. πŸ‘‘
fr fr: -ENOENT = couldn't find the thing. 0 = we're so back.

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/acpi/pptt.c, plus the whole friend group:


and that's the page, bestie 🫢 sourced from ./drivers/acpi, dated October 2026, acpi_get_cache_info(9) β€” periodt. πŸ’…β­πŸŒˆ

πŸ“¦ where this page comes from