STRUCT REGISTRY_LIST_ENTRY(9)

💖 struct registry_list_entry(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ this one's about struct registry_list_entry, and it's literally a linked list member for a registry key/value. yes that's a mouthful, no i will not be shortening it 🫶

---

🌸 SYNOPSIS 🌸

like, here's the whole vibe of the struct, don't touch a single character:

struct registry_list_entry {
    struct list_head head;
    enum registry_type type;
    size_t klen;
    char key[REGISTRY_MAX_KEY_LENGTH];
    size_t vlen;
    u32 dword;
    u8 binary[];
 };

---

🎀 Members 🎀

bestie these are the members, pay attention, there will be a quiz:

• head — the list_head struct, it's giving linked-list glue 💅
• type — it's one of dword, binary, or string
• klen — the length of the name of the key
• key — the key name itself, iconic
• vlen — the length of the value
• dword — the data, if it's REGISTRY_TABLE_ENTRY_TYPE_DWORD
• binary — the data, if it's TYPE_BINARY or TYPE_STRING

---

✨ Description ✨

every single registry key/value is represented internally by this struct. every one. no cap 💀

Type DWORD is a simple 32-bit unsigned integer, and its value is stored in dword. that's it, that's the whole personality.

Types BINARY and STRING are variable-length binary blobs 🌈 the only real difference between BINARY and STRING is that STRING is null-terminated and is expected to contain only printable characters. random bytes? not their moment. 🙈

---

👑 Note 👑

technically it is possible to have multiple keys with the same name but different types, but this is not useful since GSP-RM expects keys to have only one specific type. so like… don't. it's giving chaotic for no reason 😭

fr fr, one key = one type. that's the vibe check. ⭐

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/gsp.c
• nvkm_gsp_mem_ctor(9), add_registry(9), build_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)

---

and that's the page!! 🧚 from ./drivers/gpu/drm/nouveau/nvkm..., dated October 2026 — mwah, slay, struct registry_list_entry(9) ate and left absolutely no crumbs 💜🍓