vmw_event_f...n_seq_passed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vmw_event_f...n_seq_passed(9) πŸ’–

okay so welcome to the Kernel API Manual, bestie β€” this page is literally rockin’ the title vmw_event_f...n_seq_passed(9), dots and all. The full function name gets its main-character moment down in NAME. ✨

🌸 NAME 🌸

vmw_event_fence_action_seq_passed β€” that’s the whole name entry, bestie; the original has no extra description after the dash, so I’m not inventing one 🫢

✨ SYNOPSIS ✨

void vmw_event_fence_action_seq_passed (struct dma_fence *f , struct
       dma_fence_cb *cb );

πŸŽ€ ARGUMENTS πŸŽ€

  • f β€” the struct dma_fence that provides the timestamp for the action event. ⏰
  • cb β€” the struct dma_fence_cb callback for the action event. 🫢

πŸ’… DESCRIPTION πŸ’…

so this function gets called when the seqno of the fence has passed β€” and bestie, listen: it is always called from atomic context. ⚠️

🚨 Atomic-context alert: always from atomic context, no cap. Handle with care. πŸ’€

It queues the event on the submitter’s event list. periodt. πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹


okay that’s the whole page β€” source/version path ./drivers/gpu/drm/vmwgfx, dated October 2026. mwah, catch you later πŸ’‹πŸŒˆ

πŸ“¦ where this page comes from