tools/testing/selftests/riscv/vector/v_helpers.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/riscv/vector/v_helpers.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/riscv/vector/v_helpers.c- Extension
.c- Size
- 1998 bytes
- Lines
- 92
- 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
../hwprobe/hwprobe.hasm/vendor/thead.hstdbool.hstdlib.hstdio.hunistd.hsys/wait.h
Detected Declarations
function is_xtheadvector_supportedfunction is_vector_supportedfunction get_vr_lenfunction launch_test
Annotated Snippet
if (rc) {
perror("execve");
printf("child execve failed %d\n", rc);
exit(-1);
}
}
rc = waitpid(-1, &status, 0);
if (rc < 0) {
printf("waitpid failed\n");
return -3;
}
if ((WIFEXITED(status) && WEXITSTATUS(status) == -1) ||
WIFSIGNALED(status)) {
printf("child exited abnormally\n");
return -4;
}
return WEXITSTATUS(status);
}
Annotation
- Immediate include surface: `../hwprobe/hwprobe.h`, `asm/vendor/thead.h`, `stdbool.h`, `stdlib.h`, `stdio.h`, `unistd.h`, `sys/wait.h`.
- Detected declarations: `function is_xtheadvector_supported`, `function is_vector_supported`, `function get_vr_len`, `function launch_test`.
- 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.