tools/testing/selftests/fpu/run_test_fpu.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/fpu/run_test_fpu.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/fpu/run_test_fpu.sh- Extension
.sh- Size
- 878 bytes
- Lines
- 47
- 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
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0
#
# Load kernel module for FPU tests
uid=$(id -u)
if [ $uid -ne 0 ]; then
echo "$0: Must be run as root"
exit 1
fi
if ! which modprobe > /dev/null 2>&1; then
echo "$0: You need modprobe installed"
exit 4
fi
if ! modinfo test_fpu > /dev/null 2>&1; then
echo "$0: You must have the following enabled in your kernel:"
echo "CONFIG_TEST_FPU=m"
exit 4
fi
NR_CPUS=$(getconf _NPROCESSORS_ONLN)
if [ ! $NR_CPUS ]; then
NR_CPUS=1
fi
modprobe test_fpu
if [ ! -e /sys/kernel/debug/selftest_helpers/test_fpu ]; then
mount -t debugfs none /sys/kernel/debug
if [ ! -e /sys/kernel/debug/selftest_helpers/test_fpu ]; then
echo "$0: Error mounting debugfs"
exit 4
fi
fi
echo "Running 1000 iterations on all CPUs... "
for i in $(seq 1 1000); do
for c in $(seq 1 $NR_CPUS); do
./test_fpu &
done
done
rmmod test_fpu
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.