drm_ras_nl_l...nodes_dumpit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_ras_nl_list_nodes_dumpit(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– β€” this one's a kernel function page and it's lowkey iconic, so let's get into it 🫢


🌸 NAME 🌸

drm_ras_nl_list_nodes_dumpit β€” literally dumps all the registered RAS nodes. that's the whole vibe πŸ’…


⭐ SYNOPSIS ⭐

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

πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” the Netlink message buffer 🌈 (it's the thing we're stuffing all the node info into, bestie)
  • cb β€” the callback context for multi-part dumps ✨ (this is the one that keeps track of where we're at)

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this function does is it iterates over all the registered RAS nodes sitting in the global xarray, and appends their attributes β€” that's the ID, the name, and the type β€” straight into the given netlink message buffer πŸ”₯

it uses cb->ctx to track its progress in case the message buffer fills up, which is what gives you that multi-part dump support, no cap πŸ‘‘ and on buffer overflow? it updates the context so it can resume from the last node on the next invocation. the way it just picks up where it left off… main character energy fr fr πŸ’œ


πŸ’€ RETURN πŸ’€

  • 0 β€” slay, all the nodes fit in skb πŸŽ‰
  • number of bytes added to skb β€” the buffer filled up, so you're gonna need the multi-part continuation πŸ™ˆ
  • a negative error code β€” something went wrong, sorry bestie 😭
ngl, that middle one is the one to watch: if you get a byte count back instead of 0, the dump isn't done yet and it's asking for a continuation. iykyk πŸ’…

🧚 SEE ALSO 🧚

like, go read them, they're all part of the same little friend group πŸ“


and that's the page!! πŸŒˆπŸ’–βœ¨ this one lives in ./drivers/gpu/drm and it's dated October 2026, filed under drm_ras_nl_l...nodes_dumpit(9) β€” mwah, obsessed with her, byeee bestie πŸ«ΆπŸ‘‘

πŸ“¦ where this page comes from