build_registry(9)

💖 NAME 💖

okay so real talk — this page is build_registry(9), straight from the Kernel API Manual (section 9, so it's kernel-dev territory, not something you type in a shell, iykyk 🫶).

build_registry — create the registry RPC data. that's the whole gig. one job. iconic behavior honestly ✨

---

🎀 SYNOPSIS 🎀

void build_registry (struct nvkm_gsp *gsp , PACKED_REGISTRY_TABLE
*registry );

no cap, that's the entire signature. go off 💅

---

🌸 ARGUMENTS 🌸

• gsp — gsp pointer. bestie that is the entire description and i'm not gonna invent lore about it 🙈
• registry — pointer to the RPC payload to fill. this is the lil container you're stuffing full of registry goodness 🎀

---

🦋 DESCRIPTION 🦋

so here's the vibe: once you've already added all your registry key/value pairs, you call this function to build the RPC. that's the moment. the main character moment 🔥

the registry RPC looks like this:

┌──────────────────────────────────────────┐
│ NvU32 size;                              │
│ NvU32 numEntries;                        │
│ PACKED_REGISTRY_ENTRY                    │
│ Null-terminated key (string) for entry 0 │
└──────────────────────────────────────────┘
|Binary/string data value for entry 0    | (only if necessary)

┌──────────────────────────────────────────┐
│ PACKED_REGISTRY_ENTRY                    │
│ Null-terminated key (string) for entry 1 │
└──────────────────────────────────────────┘
|Binary/string data value for entry 1    | (only if necessary) ... (and
so on, one copy for each entry)

like… one copy for each entry. every single one. no skipping 💀

and the data field of an entry? it's either a 32-bit integer (for type DWORD) or an offset into the PACKED_REGISTRY_TABLE (for types BINARY and STRING). two paths, pick your fighter ⭐

also important, don't sleep on this: all memory allocated by add_registry is released. every byte. it's giving cleanup era 🧹✨

fr fr do not go poking at that memory afterwards, it is gone 💀

---

💜 SEE ALSO 💜

the whole friend group, in order:

• Kernel file ./drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/gsp.c
• nvkm_gsp_mem_ctor(9)
• struct registry_list_entry(9)
• add_registry(9)
• clean_registry(9)
• strip(9)
• r535_gsp_rpc_set_registry(9)
• r535_gsp_msg_run_cpu_sequencer(9)
• struct rpc_ucode_libos_print_v1e_08(9)
• r535_gsp_msg_libos_print(9)
• create_debugfs(9)
• r535_gsp_libos_debugfs_init(9)
• create_pte_array(9)
• r535_gsp_libos_init(9)
• nvkm_gsp_radix3_sg(9)
• r535_debugfs_shutdown(9)
• is_empty(9)
• r535_gsp_copy_log(9)
• r535_gsp_retain_logging(9)
• r535_gsp_libos_debugfs_fini(9)

---

mwah 💋 that's the page. sourced from ./drivers/gpu/drm/nouveau/nvkm... and dated October 2026 — go forth and build that registry, bestie, you're gonna slay 👑🌈