STRUCT CPUID_PARSE_ENTRY(9)
π¦ NAME π¦
okay so bestie, welcome to the Kernel API Manual π
β this page is all about struct cpuid_parse_entry, aka the CPUID parse table entry. literally one struct, one job, and it ate. β¨
πΈ SYNOPSIS πΈ
struct cpuid_parse_entry {
unsigned int leaf;
unsigned int subleaf;
unsigned int regs_offs;
unsigned int info_offs;
unsigned int maxcnt;
void (*read)(const struct cpuid_parse_entry *e, const struct cpuid_output *o);
};
no cap, that's the whole vibe. now let's meet the members π
π Members π
leafβ the leaf number that's getting parsed π like, this is the CPUID leaf, bestie, it's giving main character energy.subleafβ the subleaf number to be parsed π¦ the little sibling ofleaf, and yes it also matters.regs_offsβ offset withinstruct cpuid_leaveswhere the CPUID query output gets saved πΎ this is the one you pass tocpuid_table_regs_p. iykyk.info_offsβ offset withinstruct cpuid_leaveswhere the CPUID query parse info gets saved π and this one goes tocpuid_table_info_p. two offsets, two destinations, no mixing them up bestie πmaxcntβ the maximum number of output storage entries available for the CPUID query π₯ that's the cap, literally and figuratively.readβ the read function for this entry π it must save the parsed CPUID output to the passed parsed and filled. a generic implementation is provided atcpuid_read_generic, so you don't have to hand-roll it if you don't wanna π«Ά
π SEE ALSO π
- Kernel file
./arch/x86/kernel/cpu/cpuid_parser.hπ struct cpuid_output(9)π
go read those too, bestie β this struct doesn't exist in a vacuum and you know it β¨
and that's the whole page, mwah π this came from ./arch/x86/kernel/cpu, October 2026, straight outta the Kernel API Manual β slay, bye ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms