rtas_physical_attestation(9)

💫 rtas_physical_attestation(9) 💫

ok so bestie, welcome to the Kernel API Manual — yes, that's the manual name, we're in the kernel API girlies now 🫶. Today's main character is rtas_physical_attestation, and she's literally just here to call ibm,physical-attestation and fill up a work area buffer. that's it. that's the vibe. ✨

---

🌸 NAME 🌸

rtas_physical_attestation — calls ibm,physical-attestation to fill a work area buffer 🎀

---

✨ SYNOPSIS ✨

int rtas_physical_attestation (struct rtas_phy_attest_params *params );

one function, one pointer, zero drama. 💅

---

🦋 ARGUMENTS 🦋

• params — the whole personality of this call, tbh. see struct rtas_phy_attest_params for the details 👑

---

💖 DESCRIPTION 💖

okay so here's what she does: she calls ibm,physical-attestation over and over until it either errors out or successfully deposits data into the supplied work area. she's persistent, she's thorough, she ate. 🔥

she also handles RTAS retry statuses for you (iconic) and maps RTAS error statuses to reasonable errno values (also iconic, honestly).

not me about to drop the important part though — the caller is expected to invoke rtas_physical_attestation multiple times to retrieve all the data for the provided attestation command. it's giving "one chip at a time" energy, fr fr. 🍓

⚠️ and here's the caveat bestie, lowkey crucial: only one sequence should be in progress at any time. starting a new sequence will disrupt any sequence already in progress. serialization of attestation retrieval sequences is the responsibility of the caller. like, that's on you, not on her. no cap. 💀

the caller should inspect params.status to determine whether more calls are needed to complete the sequence. that's your vibe check right there — read the status, bestie. 👀

---

🌈 CONTEXT 🌈

May sleep. 😴 (yes, she's allowed. she's got main character energy and a scheduler to respect.)

---

⭐ RETURN ⭐

• -ve on error
• 0 otherwise

simple. clean. slay. ✨

---

💜 SEE ALSO 💜

• Kernel file ./arch/powerpc/platforms/pseries/papr-phy-attest.c
• struct rtas_phy_attest_params(9)
• phy_attest_sequence_begin(9)
• phy_attest_sequence_end(9)
• papr_phy_attest_create_handle(9)

the whole friend group, honestly. go read them. iykyk 🧚

---

and that's the page!! 🎀 brought to you by ./arch/powerpc/platforms/pseries, October 2026, Kernel API Manual — mwah, stay hydrated, and don't start two attestation sequences at once 💅💖