tools/testing/selftests/vfio/lib/iova_allocator.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/vfio/lib/iova_allocator.c

Extension

.c

Size

2088 bytes

Lines

94

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• dirent.h
• fcntl.h
• libgen.h
• stdint.h
• stdlib.h
• string.h
• unistd.h
• sys/eventfd.h
• sys/ioctl.h
• sys/mman.h
• linux/iommufd.h
• linux/limits.h
• linux/mman.h
• linux/overflow.h
• linux/types.h
• linux/vfio.h
• libvfio.h

Detected Declarations

• function iova_allocator_cleanup
• function iova_allocator_alloc

Annotated Snippet

if (last == range->last) {
			allocator->range_idx++;
			allocator->range_offset = 0;
		} else {
			allocator->range_offset = last - range->start + 1;
		}

		return iova;

next_range:
		allocator->range_idx++;
		allocator->range_offset = 0;
	}
}

Annotation

• Immediate include surface: `dirent.h`, `fcntl.h`, `libgen.h`, `stdint.h`, `stdlib.h`, `string.h`, `unistd.h`, `sys/eventfd.h`.
• Detected declarations: `function iova_allocator_cleanup`, `function iova_allocator_alloc`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.