append_oa_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ append_oa_status(9) β€” Kernel API Manual πŸŽ€

πŸ“ NAME πŸ“

append_oa_status β€” appends a status record to a userspace read() buffer. That’s the whole gig, and it eats every time. πŸ’…

✨ SYNOPSIS ✨

int append_oa_status (struct i915_perf_stream *stream , char __user *buf
       , size_t count , size_t *offset , enum drm_i915_perf_record_type type );

πŸŽ€ ARGUMENTS πŸŽ€

  • stream β€” an i915-perf stream that was opened for OA metrics.
  • buf β€” the destination buffer handed over by userspace.
  • count β€” the number of bytes userspace wants to read.
  • offset β€” (inout) the current position for writing into buf.
  • type β€” the kind of status to report to userspace.

πŸ’… DESCRIPTION πŸ’…

okay so picture this, bestie: append_oa_status writes a status record into the userspace read buffer. We’re talking about a status record such as DRM_I915_PERF_RECORD_OA_REPORT_LOST β€” yes, that exact one. ✨πŸ”₯

And the lil rule to remember is iconic: the buf offset will only be updated on success. No success? No offset move. Periodt. πŸ’–

🌈 RETURN 🌈

  • 0 on success. slay. πŸ‘‘
  • negative error code on failure. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

okay bestie, the whole i915 perf cinematic universe is right here:


Sign-off bestie: this page comes from ./drivers/gpu/drm/i915, it’s dated October 2026, and the manual page is append_oa_status(9). Stay perf-y. πŸ«ΆπŸ’œ
πŸ“¦ where this page comes from