rtas_ibm_platform_dump(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ rtas_ibm_platform_dump(9) β€” bestie edition ✨

okay so welcome to the Kernel API Manual page for rtas_ibm_platform_dump(9), where the assignment is literally "call ibm,platform-dump to fill a work area buffer" and we are going to understand it. πŸ’…


🌸 NAME 🌸

rtas_ibm_platform_dump β€” call ibm,platform-dump to fill a work area buffer. That's the whole vibe, no cap. πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

int rtas_ibm_platform_dump (struct ibm_platform_dump_params *params ,
phys_addr_t buf_addr , u32 buf_length );

🫢 ARGUMENTS 🫢

  • params β€” see struct ibm_platform_dump_params. πŸ‘€
  • buf_addr β€” address of the dump buffer (work_area). πŸ“
  • buf_length β€” length of the buffer in bytes (min. 1024). πŸ”’

πŸ’« DESCRIPTION πŸ’«

It calls ibm,platform-dump until it errors or successfully deposits data into the supplied work area. It handles RTAS retry statuses, and maps RTAS error statuses to reasonable errno values. Very "I got this, bestie" of it. ✨

You can request multiple dumps with different dump IDs at the same time, but not with the same dump ID β€” that's prevented with the check in the ioctl code (papr_platform_dump_create_handle). 🚫

The caller should inspect params.status to determine whether more calls are needed to complete the sequence. Yes, it's a whole "check the vibe as you go" situation. πŸ‘‘

😴 CONTEXT 😴

May sleep. Literally may sleep β€” plan accordingly. πŸ’€

πŸ”₯ RETURN πŸ”₯

  • -ve on error
  • 0 for dump complete
  • 1 for continue dump

πŸ‘‘ SEE ALSO πŸ‘‘


Cute sign-off: this page lives in the ./arch/powerpc/platforms/pseries corner of the Kernel API Manual, dated October 2026, and it's titled rtas_ibm_platform_dump(9) β€” periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from