hl_unreserve_va_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME

okay so bestie, hl_unreserve_va_block is literally a wrapper for add_va_block to unreserve a va block. That’s the whole NAME moment, no cap. And yes, this is the hl_unreserve_va_block(9) page from the Kernel API Manual β€” folding the manual name in right here so we don’t have to copy the header line, periodt. 🫢

✨ SYNOPSIS

int hl_unreserve_va_block (struct hl_device *hdev , struct hl_ctx *ctx ,
u64 start_addr , u64 size );

πŸŽ€ ARGUMENTS

  • hdev β€” pointer to the habanalabs device structure
  • ctx β€” pointer to the context structure.
  • start_addr β€” start virtual address.
  • size β€” number of bytes to unreserve.

πŸ¦‹ DESCRIPTION

This function does the following:

  • Takes the list lock and calls add_va_block_locked.

That’s the whole plot, fr fr. πŸ’…

πŸ”₯ SEE ALSO

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

the whole friend group: 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), 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).


sending u off with a footer kiss from ./drivers/accel/habanalabs/common, dated October 2026 β€” that’s the source/version + date tea, bestie πŸ’‹ mwah

πŸ“¦ where this page comes from