tools/testing/selftests/ftrace/test.d/remotes/unloading.tc
Source file repositories/reference/linux-study-clean/tools/testing/selftests/ftrace/test.d/remotes/unloading.tc
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/ftrace/test.d/remotes/unloading.tc- Extension
.tc- Size
- 683 bytes
- Lines
- 42
- 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
# description: Test trace remote unloading
# requires: remotes/test
. $TEST_DIR/remotes/functions
test_unloading()
{
# No reader, writing
assert_loaded
# No reader, no writing
echo 0 > tracing_on
assert_unloaded
# 1 reader, no writing
cat trace_pipe &
pid=$!
sleep 1
assert_loaded
kill $pid
assert_unloaded
# No reader, no writing, events
echo 1 > tracing_on
echo 1 > write_event
echo 0 > tracing_on
assert_loaded
# Test reset
clear_trace
assert_unloaded
}
if [ -z "$SOURCE_REMOTE_TEST" ]; then
set -e
setup_remote_test
test_unloading
fi
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.