intel_gvt_mm..._write_patch(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 at
  • offset β€” 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 πŸ‘‘:


🫢 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