hl_vm_init(9)

🌟 hl_vm_init(9) — Kernel API Manual 🌟

okay bestie, this is the Kernel API Manual page for hl_vm_init(9), and it’s giving “tiny function, very specific job.” Let’s get into it. 💖

---

💖 NAME 💖

hl_vm_init — initialize virtual memory module.

---

🌸 SYNOPSIS 🌸

the signature is literally this, character for character:

int hl_vm_init (struct hl_device *hdev );

---

🎀 ARGUMENTS 🎀

• hdev — pointer to the habanalabs device structure. That’s the argument vibe, no cap. 🫶

---

💫 DESCRIPTION 💫

okay so this function initializes the following — read it and weep (affectionately):

• MMU module — yep, the MMU module gets initialized. slay. ✨
• DRAM physical pages pool of 2MB — the DRAM physical pages pool of 2MB gets initialized. 🍓
• Idr for device memory allocation handles — the Idr for device memory allocation handles gets initialized too, periodt. 💅

---

🦋 SEE ALSO 🦋

if you’re going down the rabbit hole, here’s the entire SEE ALSO squad — every single one, zero skips:

• Kernel file ./drivers/accel/habanalabs/common/memory.c
• 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)
• print_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_fini(9)
• hl_hw_block_mem_init(9)
• hl_hw_block_mem_fini(9)

---

🎀 cute sign-off: source/version is ./drivers/accel/habanalabs/common, dated October 2026. That’s the footer lore, bestie — periodt. 💖