vmw_resource_dirty_update(9)

📦 version 7.3.1, in nixpkgs unstable

💖 vmw_resource_dirty_update — a Kernel API Manual moment 💖

okay so bestie, welcome to the Kernel API Manual entry for vmw_resource_dirty_update, and honestly? it's giving "quietly important little helper" and i'm obsessed 🎀

✨ NAME ✨

vmw_resource_dirty_update — updates a resource's dirty tracker with a sequential range of touched backing store memory. no cap, that's literally the whole job 💅

🌸 SYNOPSIS 🌸

void vmw_resource_dirty_update (struct vmw_resource *res , pgoff_t start
, pgoff_t end );

like look at her. void return, three args, no drama. main character energy fr fr ✨

🦋 ARGUMENTS 🦋

  • res — the resource. the actual little guy being tracked, the whole reason we're here 🫶
  • start — the first page touched. where the range begins, periodt 📍
  • end — the last page touched + 1. yes, plus one. that's the exclusive-ish end of the range, so don't come for me, it's literally in the spec 😭
lowkey important: end is last page + 1, not the last page. do NOT forget the + 1 or you will be off by one and that's the vibe killer of all vibe killers 💀

🔥 SEE ALSO 🔥

the kernel file, bestie, the actual source:

./drivers/gpu/drm/vmwgfx/vmwgfx_resource.c

and the whole friend group 💜:

and that's the page, bestie 🌈 she ships from ./drivers/gpu/drm/vmwgfx, dated October 2026, and the whole thing is filed under vmw_resource_dirty_update(9). go forth and mark your pages dirty (in the sequential range sense) 💖✨🍓

📦 where this page comes from