tools/testing/selftests/kvm/loongarch/pmu_test.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/kvm/loongarch/pmu_test.c

Extension

.c

Size

5505 bytes

Lines

206

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

• linux/bitops.h
• kvm_util.h
• pmu.h
• loongarch/processor.h

Detected Declarations

• function has_pmu_support
• function dump_pmu_caps
• function guest_pmu_base_test
• function guest_irq_handler
• function guest_pmu_interrupt_test
• function guest_code
• function main

Annotated Snippet

switch (get_ucall(vcpu, &uc)) {
		case UCALL_PRINTF:
			printf("%s", (const char *)uc.buffer);
			break;
		case UCALL_DONE:
			printf("PMU test PASSED\n");
			goto done;
		case UCALL_ABORT:
			printf("PMU test FAILED\n");
			ret = -1;
			goto done;
		default:
			printf("Unexpected exit\n");
			ret = -1;
			goto done;
		}
	}

done:
	kvm_vm_free(vm);
	return ret;
}

Annotation

• Immediate include surface: `linux/bitops.h`, `kvm_util.h`, `pmu.h`, `loongarch/processor.h`.
• Detected declarations: `function has_pmu_support`, `function dump_pmu_caps`, `function guest_pmu_base_test`, `function guest_irq_handler`, `function guest_pmu_interrupt_test`, `function guest_code`, `function main`.
• 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.