STRUCT TEE_CMD_MAP_SHARED_MEM(9)

💖 STRUCT TEE_CMD_MAP_SHARED_MEM(9) 💖

okay so quick vibe check bestie: this is a Kernel API Manual page, section 9 — yep, the big-kid kernel section ✨ (the header up top literally reads struct tee_...p_shared_mem(9), that's just the name doing a little truncation moment, we move).

---

🌸 NAME 🌸

struct tee_cmd_map_shared_mem — the command that maps shared memory. it's giving "let me put this memory on the map" and honestly? iconic 🗺️💅

---

✨ SYNOPSIS ✨

struct tee_cmd_map_shared_mem {
    u32 buf_id;
    struct tee_sg_list sg_list;
 };

no cap, that's the whole struct. two members. tiny but mighty 🫶

---

🎀 Members 🎀

• buf_id — marked [out] bestie, so this is what comes back to you: the return buffer ID value 💖
• sg_list — marked [in], so this is what you hand over: the list describing the memory to be mapped 📋✨

lowkey the [in] / [out] tags are the whole plot here — sg_list goes in, buf_id comes out. main character energy for each of them fr fr.

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/tee/amdtee/amdtee_if.h — and then the whole friend group:

• struct memref(9)
• struct tee_sg_desc(9)
• struct tee_cmd_unmap_shared_mem(9)
• struct tee_cmd_load_ta(9)
• struct tee_cmd_unload_ta(9)
• struct tee_cmd_open_session(9)
• struct tee_cmd_close_session(9)
• struct tee_cmd_invoke_cmd(9)

like, that's the entire trusted-app lifecycle in one list and they ALL showed up to the group chat 😭👑

---

and that's the page!! 🧚 source/version teas: it lives in ./drivers/tee/amdtee, dated October 2026, and the whole thing is filed under struct tee_...p_shared_mem(9) — go map that memory, bestie, slay 💜🎀