STRUCT RTAS_PHY_ATTEST_PARAMS(9)

💅 NAME 💅

struct rtas_phy_attest_params — the parameter struct (both in and out, bestie, it's giving duality ✨) for ibm,physical-attestation.

Welcome to the Kernel API Manual, gorgeous, we're doing powerpc today 💖

✨ SYNOPSIS ✨

struct rtas_phy_attest_params {
    struct papr_phy_attest_io_block cmd;
    struct rtas_work_area *work_area;
    u32 cmd_len;
    u32 sequence;
    u32 written;
    s32 status;
};

okay so like. six fields. that's it. no cap, that's the whole vibe check 🌸

🫶 Members 🫶

• cmd — In: the attestation command buffer, and you (the caller) provide it. ⚠️ Heads up though: it must be RTAS-addressable. That's not a suggestion, that's the whole ballgame — if it's not addressable by RTAS, this is not it, and I cannot stress that enough 😭
• work_area — this one's doing double duty, main character energy fr fr 👑
  • In: a caller-provided work area buffer for the attestation command structure.
  • Out: a caller-provided work area buffer for the response.
• cmd_len — In: the length of the caller-provided attestation command structure. that's the number, keep it accurate 💅
• sequence — In: sequence number. Out: the next sequence number. she comes in one way and leaves another, iconic 🦋
• written — Out: the bytes written by ibm,physical-attestation into work_area. literally the receipts 🧾
• status — Out: the RTAS call status. if you don't check this, bestie, what are you even doing 🙈

💜 SEE ALSO 💜

• Kernel file ./arch/powerpc/platforms/pseries/papr-phy-attest.c — go read the source, it's literally right there 🍓
• rtas_physical_attestation(9)
• phy_attest_sequence_begin(9)
• phy_attest_sequence_end(9)
• papr_phy_attest_create_handle(9)

slay, you made it to the end 🎀 this little bundle of joy lives in ./arch/powerpc/platforms/pseries, version October 2026, and that's the tea ☕️💖 go call your RTAS now, ily, bye 👋✨