xe_gt_sriov_vf_read32(9)

🌸 NAME 🌸

okay so this page is xe_gt_sriov_vf_read32 from the Kernel API Manual, and its whole thing is: get a register value from the runtime data. that's the vibe 💅

---

✨ SYNOPSIS ✨

u32 xe_gt_sriov_vf_read32 (struct xe_gt *gt , struct xe_reg reg );

---

🎀 ARGUMENTS 🎀

• gt — the xe_gt. literally that's the one.
• reg — the register to read. yes bestie, that register.

---

💅 DESCRIPTION 💅

okay so real talk: this function is for VF use only. no cap. 🫶

It shall be called after the VF has connected to the PF — like, that's the prerequisite, don't skip it. ✨

And it's dedicated for registers that VFs can't read directly. so it's giving "special delivery from the PF" energy, iykyk. 👑

bestie, remember the order: VF use only, call it after the VF has connected to the PF, and it's for registers VFs can't read directly. that's the whole lore. 🧚

---

⭐ RETURN ⭐

You get the register value obtained from the PF, or 0 if not found. that's it, that's the return 💖

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_vf.c
• xe_gt_sriov_vf_reset(9)
• xe_gt_sriov_vf_bootstrap(9)
• xe_gt_sriov_vf_guc_versions(9)
• xe_gt_sriov_vf_gmdid(9)
• xe_gt_sriov_vf_query_config(9)
• xe_gt_sriov_vf_sched_groups_enabled(9)
• xe_gt_sriov_vf_guc_ids(9)
• xe_gt_sriov_vf_paging_engines(9)
• xe_gt_sriov_vf_connect(9)
• xe_gt_sriov_vf_default_lrcs_hwsp_rebase(9)
• xe_gt_sriov_vf_migrated_event_handler(9)
• xe_gt_sriov_vf_query_runtime(9)
• xe_gt_sriov_vf_write32(9)
• xe_gt_sriov_vf_print_config(9)
• xe_gt_sriov_vf_print_runtime(9)
• xe_gt_sriov_vf_print_version(9)
• xe_gt_sriov_vf_init_early(9)
• xe_gt_sriov_vf_init(9)
• xe_gt_sriov_vf_recovery_pending(9)
• xe_vf_migration_fixups_complete_count(9)
• xe_gt_sriov_vf_wait_valid_ggtt(9)

---

okay bye bestie 💖 cute lil sign-off: source/version is ./drivers/gpu/drm/xe, date is October 2026, and this iconic page is xe_gt_sriov_vf_read32(9). mwah 🎀🦋