vmw_bo_pin_in_vram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, this is vmw_bo_pin_in_vram(9) from the Kernel API Manual β€” and the whole function is literally just Move a buffer to vram. ✨ Slay.


✨ SYNOPSIS ✨

no cap, here’s the signature exactly as it is β€” don’t let the line break jump-scare you:

int vmw_bo_pin_in_vram (struct vmw_private *dev_priv , struct vmw_bo
       *buf , bool interruptible );

πŸ’… ARGUMENTS πŸ’…

  • dev_priv β€” Driver private. (the driver’s private data, periodt)
  • buf β€” DMA buffer to move. (the actual buffer, bestie)
  • interruptible β€” Use interruptible wait. (yes, that exact mode πŸ’–)

πŸ¦‹ DESCRIPTION πŸ¦‹

This function takes the reservation_sem in write mode. Then it flushes and unpins the query bo to avoid failures.

That’s the whole vibe check: write-mode reservation_sem, flush + unpin the query bo, no failures please πŸ˜­πŸ’…


🌈 RETURN 🌈

Zero on success, Negative error code on failure. In particular -ERESTARTSYS if interrupted by a signal.

So if you get a negative number, that’s the failure branch β€” and if a signal interrupts you, expect -ERESTARTSYS. πŸ’€


πŸ”₯ SEE ALSO πŸ”₯


mwah πŸ’‹ cute sign-off: source/version is ./drivers/gpu/drm/vmwgfx, and the date is October 2026. bye bestie, go pin that buffer 🫢

πŸ“¦ where this page comes from