tools/testing/selftests/verification/test.d/functions
Source file repositories/reference/linux-study-clean/tools/testing/selftests/verification/test.d/functions
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/verification/test.d/functions- Extension
[no extension]- Size
- 905 bytes
- Lines
- 40
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
check_requires() { # Check required files, monitors and reactors
for i in "$@" ; do
p=${i%:program}
m=${i%:monitor}
r=${i%:reactor}
if [ $p != $i ]; then
if ! which $p ; then
echo "Required program $p is not found."
exit_unresolved
fi
elif [ $m != $i ]; then
if ! grep -wq $m available_monitors ; then
echo "Required monitor $m is not configured."
exit_unsupported
fi
elif [ $r != $i ]; then
if ! grep -wq $r available_reactors ; then
echo "Required reactor $r is not configured."
exit_unsupported
fi
elif [ ! -e $i ]; then
echo "Required feature interface $i doesn't exist."
exit_unsupported
fi
done
}
initialize_system() { # Reset RV to initial-state
echo > enabled_monitors
for m in monitors/*; do
echo nop > $m/reactors || true
done
echo 1 > monitoring_on
echo 1 > reacting_on || true
}
finish_system() {
initialize_system
}
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
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.