rtas_call_unlocked(9)

✨ rtas_call_unlocked(9) ✨

okay so this is a page from the Kernel API Manual bestie, and it's all about rtas_call_unlocked — a little function that goes and pokes RTAS firmware without doing the whole synchronization thing 💅

---

🎀 NAME 🎀

rtas_call_unlocked — literally invoke an RTAS firmware function without synchronization, no cap 🫶

---

🌸 SYNOPSIS 🌸

void rtas_call_unlocked (struct rtas_args *args , int token , int nargs
, int nret , ... );

---

🦋 ARGUMENTS 🦋

• args — the RTAS parameter block that's gonna be used for the call. it's giving "must obey RTAS addressing constraints" energy, so like, respect that fr fr 🙈
• token — identifies which function is being invoked. iykyk ✨
• nargs — how many input parameters there are. does not include the token, bestie, keep that separate 💀
• nret — how many output parameters there are, and yes that count does include the call status 👑
• ... — the actual list of nargs input parameters. slay 🌈

---

💖 DESCRIPTION 💖

so what it does is invoke the RTAS function indicated by token, and the caller should get that token via rtas_function_token. iconic behavior, no notes ⭐

it's similar to rtas_call, but here's the tea: you can only use this one with a limited set of RTAS calls that are specifically exempted from the general requirement that only one RTAS call may be in progress at any time. like, that's the whole rule and these calls are the special exceptions 🧚

examples include stop-self and ibm,nmi-interlock — those two are the main character exceptions 💜

---

🔥 SEE ALSO 🔥

• Kernel file ./arch/powerpc/kernel/rtas.c
• struct rtas_function(9)
• rtas_function_token(9)
• rtas_call(9)
• rtas_busy_delay_time(9)
• rtas_busy_delay(9)
• rtas_ibm_suspend_me(9)
• rtas_activate_firmware(9)
• get_pseries_errorlog(9)

---

okay that's the whole page, go forth and call your firmware responsibly 🍓

<cute sign-off>mwah 💋 this came from ./arch/powerpc/kernel and it's dated October 2026 — see u then, bestie 🎀✨</cute sign-off>