intel_gvt_mm..._write_patch(9)
π intel_gvt_mm..._write_patch(9)
okay so this is a page from the Kernel API Manual β yes, the intel_gvt_mm..._write_patch(9) one, the title got truncated by the shell and honestly it's giving main-character-with-a-long-name energy π
β¨ NAME β¨
intel_gvt_mmio_set_cmd_write_patch β mark an MMIO if its cmd write needs to be patched π©Ή
Like, you're literally flagging a register so the kernel knows "hey bestie, this one's cmd write needs a little patch work." No cap.
πΈ SYNOPSIS πΈ
void intel_gvt_mmio_set_cmd_write_patch (struct intel_gvt *gvt ,
unsigned int offset );
Returns void β nothing comes back, it just does the thing. Periodt. π
π¦ ARGUMENTS π¦
gvtβ a GVT device π₯οΈ like, the whole graphics virtualization thing you're poking atoffsetβ register offset π the exact spot in the register map you're marking
π₯ SEE ALSO π₯
the kernel file lives right here, go look, iykyk:
./drivers/gpu/drm/i915/gvt/gvt.h
and the whole friend group of related calls π:
intel_gvt_mmio_set_accessed(9)intel_gvt_mmio_is_cmd_accessible(9)intel_gvt_mmio_set_cmd_accessible(9)intel_gvt_mmio_is_unalign(9)intel_gvt_mmio_has_mode_mask(9)intel_gvt_mmio_is_sr_in_ctx(9)intel_gvt_mmio_set_sr_in_ctx(9)intel_gvt_mmio_is_cmd_write_patch(9)intel_gvt_read_gpa(9)intel_gvt_write_gpa(9)
π«Ά friendly reminder: intel_gvt_mmio_is_cmd_write_patch(9) is the one that checks the flag, and this page's function is the one that sets it. they're a matching set, obsessed with them honestly π
and that's the whole page bestie, mwah π β brought to you by ./drivers/gpu/drm/i915/gvt, October 2026, intel_gvt_mm..._write_patch(9) signing off πβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms