vmw_bo_fence_single(9)

📦 version 7.3.1, in nixpkgs unstable

💅 vmw_bo_fence_single(9) — like, the whole glow-up

okay so bestie, welcome to the Kernel API Manual entry for vmw_bo_fence_single(9) — yes that's the page name, yes I'm putting it right at the top so you don't get lost, you're welcome 🫶. This is one of those tiny utility functions that does exactly one job and does it iconically. Let's get into it ✨

🌸 NAME 🌸

vmw_bo_fence_single — a utility function to fence a single TTM buffer object without unreserving it. That's the whole personality, no cap 💅

✨ SYNOPSIS ✨

void vmw_bo_fence_single (struct ttm_buffer_object *bo , struct
vmw_fence_obj *fence );

literally just two pointers, one function, zero drama. we love a minimal signature 👑

🎀 ARGUMENTS 🎀

  • bo — pointer to the struct ttm_buffer_object that you want to fence. this is the main character of the operation, the buffer object in question 💖
  • fence — pointer to the fence. and here's the fun part bestie: if it's NULL, this function will insert a fence into the command stream. so like, no fence? no problem, it makes one for you 🪄✨

🦋 DESCRIPTION 🦋

so contrary to the ttm_eu version of this function, ours is a solo act — it takes only a single buffer object instead of a whole list. one bo, one vibe, no crowd 🌈

and it also doesn't unreserve the buffer object — which, real talk, means you have to do that part separately yourself. it's giving "I handled the fence, the unreserve is a you problem" 💀 but like, respectfully. don't forget it, fr fr 🙈

⭐ SEE ALSO ⭐

the kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_bo.c and its whole friend group, in order, because we're thorough queens:

go read them, they're all slay in their own way 🧚💜

quick reminder bestie: no unreserving happens here. that's a separate step. i know. i know. but them's the rules 💅

source lives under ./drivers/gpu/drm/vmwgfx, this manual page is dated October 2026, and it's filed under vmw_bo_fence_single(9) — mwah, that's the whole page, ily, bye 🍓🎀💖

📦 where this page comes from