STRUCT RTAS_IBM_GET_VPD_PARAMS(9)

💅 NAME 💅

okay bestie so welcome to the struct rtas_ibm_get_vpd_params page — this is the Kernel API Manual and this struct is literally the parameters (both in and out, she multitasks 💁‍♀️) for ibm,get-vpd. that's it, that's the whole vibe check ✨

🌸 SYNOPSIS 🌸

struct rtas_ibm_get_vpd_params {
    const struct papr_location_code *loc_code;
    struct rtas_work_area *work_area;
    u32 sequence;
    u32 written;
    s32 status;
};

no cap, that's the whole shape of her 👑

🎀 Members 🎀

• loc_code — In: a caller-provided buffer holding the location code. the one non-negotiable here: it must be RTAS-addressable, no exceptions 🫶
• work_area — In: a caller-provided work area buffer where the results land. you bring the space, RTAS brings the data 🧚
• sequence — In: the sequence number you're handing over. Out: the next sequence number comes back to you. she's giving both-directions main character energy 🔥
• written — Out: how many bytes ibm,get-vpd actually wrote into work_area. the receipts, basically 💅
• status — Out: the RTAS call status. this is the vibe check result, look at it first fr fr 👀

🦋 SEE ALSO 🦋

• Kernel file ./arch/powerpc/platforms/pseries/papr-vpd.c — the source, go read her 📖
• rtas_ibm_get_vpd(9)
• vpd_sequence_begin(9)
• vpd_sequence_end(9)
• papr_vpd_create_handle(9)

all the besties in the same friend group, go say hi 🫶✨

lowkey reminder: that loc_code buffer being RTAS-addressable is not a suggestion, it's the whole assignment 💀

and that's the page, bestie 🎀 this came out of ./arch/powerpc/platforms/pseries, dated October 2026, and if you see the header struct rtas_...t_vpd_params(9) stamped on your terminal that's just her ~truncated~ signature, she's iconic like that 💖🌈⭐