tools/testing/selftests/powerpc/eeh/eeh-vf-unaware.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/powerpc/eeh/eeh-vf-unaware.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/powerpc/eeh/eeh-vf-unaware.sh- Extension
.sh- Size
- 633 bytes
- Lines
- 36
- 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/sh
# SPDX-License-Identifier: GPL-2.0-only
. ./eeh-functions.sh
eeh_test_prep # NB: may exit
vf_list="$(eeh_enable_vfs)";
if $? != 0 ; then
log "No usable VFs found. Skipping EEH unaware VF test"
exit $KSELFTESTS_SKIP;
fi
log "Enabled VFs: $vf_list"
failed=0
for vf in $vf_list ; do
log "Testing $vf"
if eeh_can_recover $vf ; then
log "Driver for $vf supports error recovery. Unbinding..."
echo "$vf" > /sys/bus/pci/devices/$vf/driver/unbind
fi
log "Breaking $vf..."
if ! eeh_one_dev $vf ; then
log "$vf failed to recover"
failed="$((failed + 1))"
fi
done
eeh_disable_vfs
test "$failed" != 0
exit $?;
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.