UNION MSI_DOMAIN_COOKIE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay bestie, welcome to the group chat for union msi_domain_cookie(9) from the Kernel API Manual. This page is short, iconic, and a little mysterious β€” and yes, the mystery is the point. πŸŽ€


πŸŽ€ NAME πŸŽ€

union msi_domain_cookie β€” Opaque MSI domain specific data. That's it, that's the name. She's opaque, she's MSI-domain-specific, she's data. Periodt. πŸ’…

✨ SYNOPSIS ✨

Here's the exact struct shape, bestie β€” no cap, this is the whole vibe:

       union msi_domain_cookie {
           u64 value;
           void *ptr;
           void __iomem *iobase;
        };

πŸ‘― Members πŸ‘―

  • value β€” the u64 value store. Literally a store for a u64 value, sitting right there in the union. πŸ’–
  • ptr β€” Pointer to domain specific data. A pointer bestie with domain-specific data on the other end. 🫢
  • iobase β€” Domain specific IOmem pointer. Yep, the domain-specific I/O memory pointer. ✨

🌸 Description 🌸

The content of this data is implementation defined, bestie β€” the implementation decides what goes in there. It's used by the MSI domain to store domain specific information which is requried for interrupt chip callbacks. (Yes, the manpage really says requried; I'm keeping the lore, not fixing the spelling. 😭)

πŸ¦‹ SEE ALSO πŸ¦‹


xoxo, bestie β€” this one's from ./include/linux, dated October 2026. πŸ’–πŸŒ·βœ¨

πŸ“¦ where this page comes from