STRUCT XE_TILE_SRIOV_VF_SELFCONFIG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct xe_tile_sriov_vf_selfconfig β€” like, the whole thing, bestie

okay so this is a page out of the Kernel API Manual and it's about one struct, and honestly? she's small but she's mighty. it's giving "little black dress of SR-IOV" ngl. let's get into it ✨


🌸 NAME 🌸

struct xe_tile_sriov_vf_selfconfig β€” VF configuration data. periodt. that's the whole personality: it's the struct that holds the config info for a VF. πŸŽ€


✨ SYNOPSIS ✨

look at her. she's literally three u64s and a dream:

struct xe_tile_sriov_vf_selfconfig {
    u64 ggtt_base;
    u64 ggtt_size;
    u64 lmem_size;
 };

no cap, that's the entire struct. iconic behavior. πŸ’…


πŸ¦‹ Members πŸ¦‹

okay so these are her fields, one by one, and yes we're doing all three because we don't skip:

  • ggtt_base β€” the assigned base offset of the GGTT region. that's it, that's the vibe. this is where the GGTT region starts, fr fr. πŸ“
  • ggtt_size β€” the assigned size of the GGTT region. so like… how big the GGTT region is. the way that these two are literally a matched set, i can't 😭
  • lmem_size β€” the assigned size of the LMEM. yep. the size. of the LMEM. assigned. we love a clear label. πŸ’–
lowkey every single one of these says "assigned" because that's the whole point β€” these values get assigned, they're not something the struct makes up out of nowhere. respect the assignment. 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

if you wanna go read the source (and bestie, you should, main character energy only):

  • Kernel file ./drivers/gpu/drm/xe/xe_tile_sriov_vf_types.h β€” that's where she lives 🏠

that's the whole page!! go be a VF configuration data knower now, i'm obsessed with your brain πŸ’œπŸ§šβ€β™€οΈ

β€” cute lil sign-off 🌈 β€”

this treasure came to you from the ./drivers/gpu/drm/xe source, October 2026 edition, and the header up top literally read struct xe_ti...f_selfconfig(9) (yes the truncation is canon, don't @ me πŸ’€). now go forth and slay, bestie πŸŽ€βœ¨

πŸ“¦ where this page comes from