drm_modeset...nterruptible(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ drm_modeset...nterruptible(9) πŸ’œ

ok so this is a page from the Kernel API Manual bestie, and we're talking about drm_modeset_lock_single_interruptible β€” yes the name is a whole mouthful, the manpage header literally abbreviates it to drm_modeset...nterruptible(9) because even the docs gave up 😭. anyway. it's a DRM modeset locking thing. let's get into it πŸŽ€


✨ NAME ✨

drm_modeset_lock_single_interruptible β€” take a single modeset lock 🫢

like literally just one (1) lock. singular. iconic.


🌸 SYNOPSIS 🌸

int drm_modeset_lock_single_interruptible (struct drm_modeset_lock *lock
);

it returns an int, it takes a pointer to a struct drm_modeset_lock named lock, that's the whole vibe ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lock β€” the lock to take. that's it. that's the argument. the lock you want. go get it bestie πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea β˜• β€” this function behaves exactly like drm_modeset_lock with a NULL context, BUT (and this is the main character detail) it performs interruptible waits.

so like, same energy as drm_modeset_lock with NULL context, but if you're waiting on it, you can be interrupted. no cap. πŸ™ˆ

it returns 0 on success, or -ERESTARTSYS when interrupted. those are the only two moods. 😭

⭐ SEE ALSO ⭐

like the whole modeset lock friend group fr fr πŸ’–


ok that's the page!! this one's from the Kernel API Manual, source dir ./drivers/gpu/drm, dated October 2026 β€” mwah, slay, periodt, go take your single lock responsibly πŸ‘‘πŸ’…βœ¨

πŸ“¦ where this page comes from