X86_MATCH_VFM(9)
π X86_MATCH_VFM(9) β like, the Kernel API Manual page, bestie β¨
okay so picture this: you're deep in the kernel, you cracked open the Kernel API Manual, and you found the page for X86_MATCH_VFM(9) β the macro that matches a CPU by its encoded vendor/family/model. it's giving cpu-matching royalty π and honestly it's lowkey iconic. let's get into it π«Ά
β¨ NAME β¨
X86_MATCH_VFM β match encoded vendor/family/model π
like literally that's the whole vibe. you give it a vfm, it matches. no cap.
πΈ SYNOPSIS πΈ
X86_MATCH_VFM (vfm , data );
that's it. that's the whole function signature. clean, simple, ate. π
π ARGUMENTS π
vfmβ the encoded value, bestie: 8 bits each for vendor, family, and model. yes, eight bits apiece, packed together like a little friendship bracelet of CPU identity π.dataβ driver specific data, orNULLif you've got nothing to say (valid, honestly π). heads up tho: the internal storage format isunsigned long, so whatever you supply β value, pointer, whatever β it gets cast tounsigned longinternally. so like, don't be surprised, iykyk β¨.
π¦ SEE ALSO π¦
the whole fam is here and they're all so valid π β kernel file ./arch/x86/include/asm/cpu_device_id.h, plus:
X86_MATCH_CPU(9)X86_MATCH_VENDOR_FAM_FEATURE(9)X86_MATCH_VENDOR_FEATURE(9)X86_MATCH_FEATURE(9)X86_MATCH_VENDOR_FAM_MODEL(9)X86_MATCH_VENDOR_FAM(9)X86_MATCH_VFM_STEPS(9)X86_MATCH_VFM_FEATURE(9)X86_MATCH_VFM_CPU_TYPE(9)
go read them, they're all main character energy in their own way π§ββοΈ
fr fr bestie, this is the whole page β nothing more, nothing less. every detail stays, the vibe is just better now πβ¨
mwah π this page came from ./arch/x86/include/asm and it's dated October 2026 β you're welcome, from the Kernel API Manual girlies ππ see u in the next manpage, ily!! π«Ά
π¦ 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