papr_platfor...reate_handle(9)

🌸 NAME 🌸

papr_platform_dump_create_handle — create a fd-based handle for reading platform dump. Okay so this is from the Kernel API Manual, and it's literally giving "here's a file descriptor so you can read a platform dump" energy. 💅

---

✨ SYNOPSIS ✨

long papr_platform_dump_create_handle (u64 dump_tag );

---

🎀 ARGUMENTS 🎀

• dump_tag — the Dump ID for the dump you're asking the hypervisor to retrieve. That's the whole vibe: you pick the dump by ID. 🫶

---

💖 DESCRIPTION 💖

Bestie, this is the handler for the PAPR_PLATFORM_DUMP_IOC_CREATE_HANDLE ioctl command. It allocates an RTAS parameter struct and work area, and attaches them to the file descriptor so user space can read with the multiple RTAS calls until the dump is completed. The memory allocation gets freed when the file is released — no leaky vibes, we love that. ✨

Multiple dump requests with different IDs are allowed at the same time, but not with the same dump ID. So if user space already has an opened file descriptor for that specific dump ID, the next request returns -EALREADY. Periodt. 🚫

---

🔥 RETURN 🔥

The installed fd number if successful, -ve errno otherwise. That's the whole return story — fd on success, negative errno when it's not giving. 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./arch/powerpc/platforms/pseries/papr-platform-dump.c
• struct ibm_platform_dump_params(9)
• rtas_ibm_platform_dump(9)

---

okay bye bestie, this lil page comes from ./arch/powerpc/platforms/pseries, dated October 2026, and it's the papr_platfor...reate_handle(9) manual page — iconic, no cap. 🎀💖✨