vmw_bo_dirty_unmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vmw_bo_dirty_unmap(9) πŸ’…

okay so this is a page from the Kernel API Manual, bestie, and it's about exactly one (1) little function. let's get into it 🫢


✨ NAME ✨

vmw_bo_dirty_unmap β€” clears, like, all the ptes pointing to a range inside a bo. yes all of them. no crumbs left. 🧹


🌸 SYNOPSIS 🌸

void vmw_bo_dirty_unmap (struct vmw_bo *vbo , pgoff_t start , pgoff_t
       end );

it's giving void, it's giving three args, it's giving absolutely no return value. iconic behavior honestly. ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • vbo β€” the buffer object. that's the whole vibe. the main character of this function, fr.
  • start β€” the first page of the range you're working with, within the buffer object.
  • end β€” the last page of the range within the buffer object + 1. yes, plus one. it's a half-open range bestie, don't come for me, that's just how it is πŸ’€
careful with that + 1 β€” it is not optional and it is not a typo, i promise you πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so this is basically ttm_bo_unmap_virtual, except β€” and this is the whole point β€” it takes a subrange instead of the whole thing. like yeah sure you could nuke everything, but we're being selective today. main character energy only for the pages in start..end. πŸ’…

lowkey that's it. that's the function. obsessed with the efficiency honestly. πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

here's the friend group, the whole squad, the found family:

go read those too, iykyk πŸ’–


aaaand that's the page!! this one lives over in ./drivers/gpu/drm/vmwgfx, dated October 2026, and it's literally called vmw_bo_dirty_unmap(9) in case you forgot already. mwah, go clear some ptes for me πŸ§šπŸ’œ

πŸ“¦ where this page comes from