vmw_cotable_scrub(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vmw_cotable_scrub β€” a Kernel API Manual moment ✨

okay so bestie, welcome to the section 9 glow-up of vmw_cotable_scrub, brought to you by the Kernel API Manual πŸ’… this one's lowkey niche (it's giving "you either know vmwgfx or you don't, iykyk") but she's iconic and we're gonna get into it πŸŽ€


✨ NAME ✨

vmw_cotable_scrub β€” scrub the cotable from the device 🧚 no cap, that's literally the whole job.


πŸ¦‹ SYNOPSIS πŸ¦‹

int vmw_cotable_scrub (struct vmw_resource *res , bool readback );

🌸 ARGUMENTS 🌸

  • res β€” pointer to the cotable resource, bestie. that's the main character here πŸ‘‘
  • readback β€” a bool that decides whether to initiate a readback of the cotable data into the backup buffer. like, do we want a lil copy for later or not πŸ™ˆ

⭐ DESCRIPTION ⭐

so in some situations β€” context swapouts, specifically β€” it might be desirable to make the device forget about the cotable without doing a full unbind. and the reason is honestly so valid: a full unbind requires reserved backup buffers, and it might not be possible to reserve them because of locking order violation issues 😭 messy.

so vmw_cotable_scrub implements a partial unbind that doesn't need that requirement β€” but it comes with the following restrictions, and no, you can't skip them, periodt:

  1. Before the cotable is again used by the GPU, vmw_cotable_unscrub must be called. like, non-negotiable βœ‹
  2. Before the cotable backing buffer is used by the CPU, or during the resource destruction, vmw_cotable_unbind must be called. also non-negotiable πŸ’€
bestie these aren't suggestions, they're the whole vibe check. skip them and that's on you 🫢

🌈 SEE ALSO 🌈


and that's the page, bestie πŸ’– this lil icon lives in ./drivers/gpu/drm/vmwgfx, dated October 2026, and she ate. mwah πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from