SSAM_VDEV(9)

📦 version 7.3.1, in nixpkgs unstable

💅 SSAM_VDEV 💅

okay so this is a page from the Kernel API Manual — yes, the kernel has its own manual, she's iconic like that — and today's main character is SSAM_VDEV, a macro that sets up a virtual device match id for you. bestie, let's get into it 🫶

✨ NAME ✨

SSAM_VDEV — Initialize a &struct ssam_device_id as virtual device with the given parameters. literally that's the whole job and she does it flawlessly 💖

🌸 SYNOPSIS 🌸

SSAM_VDEV (cat , tid , iid , fun );

🎀 ARGUMENTS 🎀

  • cat — the target category of the device 🐱 (no, not that kind of cat, it's a category, but slay)
  • tid — the target ID of the device
  • iid — the instance ID of the device
  • fun — the sub-function of the device ✨

🦋 DESCRIPTION 🦋

so what she does: initializes a struct ssam_device_id with the given parameters in the virtual domain. that's the vibe 💫

if you wanna know the details on what these parameters actually mean, go look at struct ssam_device_uid — she has the lore.

now here's the cute part: you can pass these special values —

  • SSAM_SSH_TID_ANY
  • SSAM_SSH_IID_ANY
  • SSAM_SSH_FUN_ANY

— to say "matching should ignore target ID / instance ID / and-or sub-function, respectively" 🙈 like, don't even look at that field, we're not checking it, periodt.

and this macro also initializes the match_flags field based on the given parameters. she's doing extra credit and honestly? we love that for her 👑

🔥 NOTE 🔥

read this part carefully bestie, no skimming:

  • cat must be a valid u8 value.
  • tid, iid, and fun must be either valid u8 values or SSAM_SSH_TID_ANY, SSAM_SSH_IID_ANY, or SSAM_SSH_FUN_ANY, respectively.
other non-u8 values are not allowed. not "eh probably fine", not "she'll figure it out" — not allowed. fr fr 💀

🌈 SEE ALSO 🌈

the whole friend group, in no particular order 💜:

and that's the page!! source is ./include/linux/surface_aggreg... and it's dated October 2026 — go read the rest of the docs bestie, ily, bye 💖🎀✨

📦 where this page comes from