hl_get_va_range_type(9)

💅 hl_get_va_range_type(9) 💅

okay so this is the Kernel API Manual, and we're doing the hl_get_va_range_type moment — it's giving “small function, very specific job” energy. No cap. 🫶

🌸 NAME 🌸

hl_get_va_range_type — get va_range type for the given address and size.

🎀 SYNOPSIS 🎀

int hl_get_va_range_type (struct hl_ctx *ctx , u64 address , u64 size ,
       enum hl_va_range_type *type );

✨ ARGUMENTS ✨

• ctx — the context to fetch va_range from, bestie.
• address — the start address of the area we want to validate.
• size — the size in bytes of the area we want to validate.
• type — the returned va_range type.

🔥 RETURN 🔥

true if the area is inside a valid range, false otherwise. That's the whole return vibe. 😌

👑 SEE ALSO 👑

go peek at these, iykyk:

• 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_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)

mwah 💋 — this page lives under ./drivers/accel/habanalabs/common, dated October 2026, and it's the hl_get_va_range_type(9) manual page. bye bestie 🦋