X86_MATCH_VE..._FAM_FEATURE(9)

📦 version 7.3.1, in nixpkgs unstable

💅 X86_MATCH_VE..._FAM_FEATURE 💅

okay so bestie, welcome to the X86_MATCH_VE..._FAM_FEATURE(9) page — that's section 9 of the Kernel API Manual, iykyk 🎀 this is the macro that lets you match a CPU on vendor, family, and feature, all at once. iconic triple-threat behaviour, honestly ✨

🌸 NAME 🌸

X86_MATCH_VENDOR_FAM_FEATURE — the macro for matching vendor, family and CPU feature. three things. one macro. slay 💅

✨ SYNOPSIS ✨

X86_MATCH_VENDOR_FAM_FEATURE (vendor , family , feature , data );

that's the whole vibe check right there 🦋 four args, no cap.

🍓 ARGUMENTS 🍓

  • vendor — the vendor name, fr fr. like INTEL, AMD, HYGON, ..., and ANY. lowkey the cute part: the name gets expanded to X86_VENDOR_vendor internally, so you just write the short one and let the macro do its little transformation moment ✨
  • family — the family number, or X86_FAMILY_ANY if you're not trying to be picky about families (understandable, live your truth) 💖
  • feature — a X86_FEATURE bit. one bit. that's the whole thing 👑
  • data — driver specific data, or NULL if you've got nothing to say 🙈. heads up: the internal storage format is unsigned long, and whatever you supply — value, pointer, etc. — gets casted to unsigned long internally. so like, it's giving "trust the process" 🌈

🦋 SEE ALSO 🦋

the whole matching macro family is right there, go read them, they're all main character energy in their own way 🫶

ngl bestie, if you're here you're probably writing a CPU device id table — and honestly? obsessed with your dedication to arch-specific details 💀🔥

mwah 💋 that's the page! this one lives at ./arch/x86/include/asm, dated October 2026, and it's filed under X86_MATCH_VE..._FAM_FEATURE(9) — yes the title is truncated with ..., no that's not a typo, that's just how the man page rendering does it 😭 go forth and match your vendors, families and features, periodt 💜

📦 where this page comes from