print_va_list_locked(9)

🎀 NAME 🎀

Hii bestie, welcome to print_va_list_locked(9) from the Kernel API Manual! This one is literally the print virtual addresses list helper — tiny, iconic, and very much a “read the lock note” situation. 💅

---

✨ SYNOPSIS ✨

No cap, this is the whole signature:

void print_va_list_locked (struct hl_device *hdev , struct list_head *va_list );

---

🫶 ARGUMENTS 🫶

• hdev — the habanalabs device structure. That’s the device bestie we’re working with. 💖
• va_list — list of virtual addresses to print. Yes, the actual list getting its moment. ✨

---

💅 DESCRIPTION 💅

okay so, this function does the following:

• Iterate over the list and print each virtual addresses block.

That’s the whole vibe: loop through the list, print every virtual addresses block. Slay. 🦋

🚨 Lock vibe check: This function should be called only when va_list lock is taken. Like, seriously — lock first, then call. No skipping this, bestie. 🔥

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/accel/habanalabs/common/memory.c

Also lowkey obsessed with these references, all in their exact little (9) era:

dma_map_host_va(9), dma_unmap_host_va(9), dram_pg_pool_do_release(9), free_phys_pg_pack(9), free_device_memory(9), clear_va_list_locked(9), merge_va_blocks_locked(9), add_va_block_locked(9), add_va_block(9), is_hint_crossing_range(9), get_va_block(9), hl_get_va_range_type(9), hl_unreserve_va_block(9), init_phys_pg_pack_from_userptr(9), map_phys_pg_pack(9), unmap_phys_pg_pack(9), map_device_va(9), unmap_device_va(9), hl_hw_block_mmap(9), export_dmabuf_from_addr(9), allocate_timestamps_buffers(9), hl_pin_host_memory(9), hl_userptr_delete_list(9), hl_userptr_is_pinned(9), va_range_init(9), va_range_fini(9), vm_ctx_init_with_ranges(9), hl_vm_ctx_fini(9), hl_vm_init(9), hl_vm_fini(9), hl_hw_block_mem_init(9), hl_hw_block_mem_fini(9)

💖 cute little footer sign-off: source/version line ./drivers/accel/habanalabs/common, date October 2026, manual print_va_list_locked(9) — byeee, bestie! 🫶