vmw_stream_claim_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vmw_stream_claim_ioctl β€” the kernel API manual, bestie edition ✨

Okay so real talk, this page is about vmw_stream_claim_ioctl(9) in the kernel API manual, and it's genuinely such a neat little function. Buckle up πŸŽ€


🌸 NAME 🌸

vmw_stream_claim_ioctl β€” the ioctl that claims a struct vmw_stream overlay. That's it, that's the whole vibe. It goes and claims one (1) overlay for you and honestly? iconic. πŸ‘‘


✨ SYNOPSIS ✨

int vmw_stream_claim_ioctl (struct drm_device *dev , void *data , struct
drm_file *file_priv );

Note the line break in the middle of the signature β€” that's the original formatting, not me being chaotic (for once πŸ™ˆ). Copy it exactly if you're typing it out.


πŸ¦‹ ARGUMENTS πŸ¦‹

Here's the whole squad of parameters, no cap:

  • dev β€” a pointer to the drm device. Like, the device itself, the main character of this whole operation πŸ’–
  • data β€” the ioctl argument. Yes, it's a void *. Yes, that's just how it is. Go with it 🫢
  • file_priv β€” a pointer to a struct drm_file that identifies the caller. Like a little name tag for whoever's asking πŸ‘‘

πŸ”₯ RETURN πŸ”₯

  • 0 if it's successful. slay πŸ’…
  • A negative error value if it fails. not slay 😭 (note that it's a negative error value, so keep an eye on that sign, bestie)

🌈 SEE ALSO 🌈

All the related lore, fr fr:

Go read those next, iykyk 🧚


Lowkey the whole page is just those five sections. No hidden OPTIONS, no sneaky BUGS section, no environment variables hiding in the walls. What you see is what you get, and what you get is a very tidy little ioctl doc ✨

Okay that's a wrap bestie πŸ“ this little gem lives under ./drivers/gpu/drm/vmwgfx and the page is dated October 2026 β€” go forth and claim those streams πŸ’œπŸ’…

πŸ“¦ where this page comes from