tools/testing/selftests/kvm/include/timer_test.h

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/kvm/include/timer_test.h

Extension

.h

Size

1012 bytes

Lines

46

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

• kvm_util.h

Detected Declarations

• struct test_args
• struct test_vcpu_shared_data

Annotated Snippet

struct test_args {
	u32 nr_vcpus;
	u32 nr_iter;
	u32 timer_period_ms;
	u32 migration_freq_ms;
	u32 timer_err_margin_us;
	/* Members of struct kvm_arm_counter_offset */
	u64 counter_offset;
	u64 reserved;
};

/* Shared variables between host and guest */
struct test_vcpu_shared_data {
	u32 nr_iter;
	int guest_stage;
	u64 xcnt;
};

extern struct test_args test_args;
extern struct kvm_vcpu *vcpus[];
extern struct test_vcpu_shared_data vcpu_shared_data[];

struct kvm_vm *test_vm_create(void);
void test_vm_cleanup(struct kvm_vm *vm);

#endif /* SELFTEST_KVM_TIMER_TEST_H */

Annotation

• Immediate include surface: `kvm_util.h`.
• Detected declarations: `struct test_args`, `struct test_vcpu_shared_data`.
• 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.