X86_MATCH_VFM_CPU_TYPE(9)

💖 X86_MATCH_VFM_CPU_TYPE(9) 💖

okay so bestie, welcome to X86_MATCH_VFM_CPU_TYPE(9) from the Kernel API Manual. This one is lowkey a baddie: it matches an encoded vendor/family/model/type combo, and the whole page is short enough to read before your iced coffee melts. 🧊✨

🌸 NAME 🌸

X86_MATCH_VFM_CPU_TYPE — matches the encoded vendor/family/model/type. That's it, that's the name, and it ate. 💅

✨ SYNOPSIS ✨

Here's the call, copied exactly so you can't mess it up:

X86_MATCH_VFM_CPU_TYPE (vfm , type , data );

🎀 ARGUMENTS 🎀

• vfm — the encoded combo, with 8-bits each for vendor, family, model. So yes: vendor + family + model all packed in there. 🫶
• type — the CPU type, e.g. P-core, E-core. That's the core flavor, bestie. 🔥
• data — driver specific data or NULL. The internal storage format is unsigned long. The supplied value, pointer etc. is cast to unsigned long internally. No cap, that cast is happening. 💀

👑 SEE ALSO 👑

The kernel file to peek at is ./arch/x86/include/asm/cpu_device_id.h. Here's the whole related-macro crew, no cap:

• 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(9)
• X86_MATCH_VFM_STEPS(9)
• X86_MATCH_VFM_FEATURE(9)

Source/version tea: ./arch/x86/include/asm · date: October 2026 · footer tag: X86_MATCH_VFM_CPU_TYPE(9). That's the whole page, bestie — go match some encoded vendor/family/model/type and slay. 💖✨