intel_vgpu_r...r_page_track(9)

💅 NAME 💅

intel_vgpu_register_page_track — bestie, this is the one that registers a guest page to be tacked ✨ (yes, the manpage says "tacked" and honestly? iconic, we're keeping it fr fr). It lives in the Kernel API Manual, and it's giving "let me put this page on the tracker list so the handler can vibe-check it later" 🎀

✨ SYNOPSIS ✨

int intel_vgpu_register_page_track (struct intel_vgpu *vgpu , unsigned
       long gfn , gvt_page_track_handler_t handler , void *priv );

Okay so you hand it a vgpu, a gfn, a handler, and some priv — and it does the registration thing. Slay 💅

🦋 ARGUMENTS 🦋

• vgpu — a vGPU. Like, the actual virtual GPU we're doing all this for 👑
• gfn — the gfn of guest page. This is the page we're putting on the tracker, no cap.
• handler — page track handler. The lil callback situation that handles the tracking 🫶
• priv — tracker private. Your own private stash of data that gets passed along, iykyk 🙈

🌸 RETURN 🌸

Returns zero on success, and a negative error code if failed. That's it, that's the vibe check: 0 = ate, negative = 💀

⭐ SEE ALSO ⭐

• Kernel file ./drivers/gpu/drm/i915/gvt/page_track.c — the source, go read it bestie 📖
• intel_vgpu_find_page_track(9)
• intel_vgpu_unregister_page_track(9)
• intel_vgpu_enable_page_track(9)
• intel_vgpu_disable_page_track(9)
• intel_vgpu_page_track_handler(9)

🧚 Lowkey the whole page-track friend group is listed above — find, unregister, enable, disable, and the handler itself. Go say hi to all of them 💜

And that's the whole page, bestie — brought to you by ./drivers/gpu/drm/i915/gvt, dated October 2026, titled intel_vgpu_r...r_page_track(9). Periodt. 💖✨