frontbuffer_flush(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… frontbuffer_flush β€” the kernel API manual, but make it make sense

okay so real talk, this is frontbuffer_flush(9) from the Kernel API Manual, and honestly? she's short but she matters. let's get into it πŸŽ€


🌸 NAME 🌸

frontbuffer_flush β€” flush frontbuffer. that's it, that's the vibe. she flushes. πŸ’…


✨ SYNOPSIS ✨

void frontbuffer_flush (struct intel_display *display , unsigned int
frontbuffer_bits , enum fb_op_origin origin );

like, look at her go 🫢 three args, returns void, no drama.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • display β€” display device. the whole display situation, bestie. πŸ–₯️
  • frontbuffer_bits β€” frontbuffer plane tracking bits. this is the "which planes are we even talking about" bitfield, keep up. ✨
  • origin β€” which operation caused the flush. like, why are we flushing? she wants to know. πŸ”

πŸ’– DESCRIPTION πŸ’–

okay so this function gets called every single time rendering on the given planes has completed and frontbuffer caching can be started again. every time. no cap. ⭐

and here's the part that's giving main character energy: flushes will get delayed if they're blocked by some outstanding asynchronous rendering. so if you're sitting there like "why hasn't it flushed 😭" β€” bestie, something async is still cooking. πŸ”₯

also the icon that she is: can be called without any locks held. no lock anxiety, no "not me forgetting to unlock", just vibes. 🧚


πŸ‘‘ SEE ALSO πŸ‘‘

like, the whole friend group honestly 🌈


ngl, this page is short β€” but every line is doing its job. don't skip the "no locks held" part, it's lowkey the most important sentence here. πŸ’€

✨ that's the whole page, bestie ✨ this cutie lives in ./drivers/gpu/drm/i915/display, dated October 2026, and she's frontbuffer_flush(9) β€” periodt. πŸ“πŸ’…

πŸ“¦ where this page comes from