xe_bo_vma_count_inc_locked(9)
π xe_bo_vma_count_inc_locked(9) π
okay bestie, welcome to the Kernel API Manual β this is the page for xe_bo_vma_count_inc_locked(9), and it is literally about accounting a new VMA on a BO. yes, we are doing bookkeeping and we are gonna slay it π
β¨
π NAME π
xe_bo_vma_count_inc_locked β Account a new VMA on a BO.
πΈ SYNOPSIS πΈ
void xe_bo_vma_count_inc_locked (struct xe_bo *bo );
β¨ ARGUMENTS β¨
boβ Buffer object. that is thestruct xe_bo *from the synopsis, bestie π«Ά
π¦ DESCRIPTION π¦
okay so the whole move here: it increments vma_count. that is it. that is the vibe β¨
β οΈ but fr fr, the caller must hold the BO's dma-resv lock. this is a locked-context situation, no cap β do not come in here without it ππ
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_bo.henum xe_madv_purgeable_state(9)xe_bo_is_purged(9)xe_bo_madv_is_dontneed(9)xe_bo_willneed_get_locked(9)xe_bo_willneed_put_locked(9)xe_bo_vma_count_dec_locked(9)xe_bo_size(9)xe_bo_has_valid_ccs_bb(9)xe_bo_put_deferred(9)xe_bo_put_async(9)xe_bo_sg_is_contiguous(9)struct xe_bo_shrink_flags(9)xe_bo_is_mem_type(9)
byeeee, source/version is ./drivers/gpu/drm/xe, date is October 2026, and the page title is xe_bo_vma_count_inc_locked(9). mwah πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms