drm_ras_nl_...unter_dumpit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

Okay bestie, gather round β€” this page is literally the Kernel API Manual entry for drm_ras_nl_get_error_counter_dumpit, and its whole job is: dump all Error Counters ✨ (yes, the header on this page is genuinely truncated mid-word β€” drm_ras_nl_...unter_dumpit(9) β€” and we're just gonna vibe with that, no cap 😭)


πŸŽ€ SYNOPSIS πŸŽ€

int drm_ras_nl_get_error_counter_dumpit (struct sk_buff *skb , struct
       netlink_callback *cb );

🌸 ARGUMENTS 🌸

  • skb β€” the Netlink message buffer, aka the little envelope everything gets stuffed into πŸ’Œ
  • cb β€” the callback context, and specifically the thing that makes multi-part dumps possible 🫢

✨ DESCRIPTION ✨

So here's the tea: this function walks over all the error counters in a given Node and appends each one's attributes β€” that's the ID, the name, and the value β€” onto the netlink message buffer you handed it. Every single one, no skipping, we're thorough like that πŸ’…

It keeps its place using cb->ctx to track progress, which matters big time in case the message buffer fills up β€” that's how the whole multi-part dump situation works πŸ‘‘

And on buffer overflow? It updates the context so the next invocation picks right back up from the last node. Resume-from-where-we-left-off energy, lowkey iconic 🌈


πŸ”₯ RETURN πŸ”₯

  • 0 β€” if all the errors fit in skb, we're done, slay, go home πŸŽ‰
  • the number of bytes added to skb β€” if the buffer filled up, which means you do need a multi-part continuation (it's giving "to be continued…" πŸ¦‹)
  • a negative error code β€” if something went wrong 😭

πŸ‘‘ SEE ALSO πŸ‘‘


fr fr go read those if you want the full lore, iykyk πŸ’–

Okay that's the whole page, bestie β€” it lives over in ./drivers/gpu/drm and this version is dated October 2026. Mwah, mwah, go dump some counters, periodt πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from