X86_MATCH_VENDOR_FAM(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ X86_MATCH_VENDOR_FAM ✨

okay so bestie, welcome to the X86_MATCH_VENDOR_FAM(9) page from the Kernel API Manual πŸ’… this one is short and sweet and honestly iconic β€” it's literally the macro that matches a CPU by vendor and family, and it eats every single time πŸ“


🌸 NAME 🌸

X86_MATCH_VENDOR_FAM β€” match vendor and family, no cap 🫢


πŸŽ€ SYNOPSIS πŸŽ€

X86_MATCH_VENDOR_FAM (vendor , family , data );

like yes, that's the whole vibe check right there ✨ three args, zero drama.


πŸ’– ARGUMENTS πŸ’–

  • vendor β€” the vendor name, bestie! things like INTEL, AMD, HYGON, ..., and ANY πŸ¦‹ and here's the cute part: the name gets expanded to X86_VENDOR_vendor πŸ”₯ so it's giving "you write the short version, the macro does the glow-up."
  • family β€” the family number, or X86_FAMILY_ANY if you're in your "idc, any family works" era πŸ’€
  • data β€” driver-specific data, or NULL if you've got nothing to say πŸ™ˆ the internal storage format is unsigned long, and whatever you supply β€” value, pointer, etc. β€” gets casted to unsigned long internally ⭐ so just know it's all getting squished into an unsigned long on the inside, iykyk.

πŸ‘‘ SEE ALSO πŸ‘‘

go check out the kernel file ./arch/x86/include/asm/cpu_device_id.h for the full lore πŸ“– and then these sibling macros, because family:

like literally the whole friend group, obsessed πŸ’œ


and that's the page, bestie 🌈 it lives under ./arch/x86/include/asm and this version is dated October 2026 β€” main character energy from the kernel docs, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from