tools/perf/tests/workloads/leafloop.c
Source file repositories/reference/linux-study-clean/tools/perf/tests/workloads/leafloop.c
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/tests/workloads/leafloop.c- Extension
.c- Size
- 749 bytes
- Lines
- 47
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
Dependency Surface
signal.hstdlib.hlinux/compiler.hunistd.h../tests.h
Detected Declarations
function sighandlerfunction leaffunction parentfunction leafloop
Annotated Snippet
#include <signal.h>
#include <stdlib.h>
#include <linux/compiler.h>
#include <unistd.h>
#include "../tests.h"
/* We want to check these symbols in perf script */
noinline void leaf(volatile int b);
noinline void parent(volatile int b);
static volatile int a;
static volatile sig_atomic_t done;
static void sighandler(int sig __maybe_unused)
{
done = 1;
}
noinline void leaf(volatile int b)
{
while (!done)
a += b;
}
noinline void parent(volatile int b)
{
leaf(b);
}
static int leafloop(int argc, const char **argv)
{
int sec = 1;
if (argc > 0)
sec = atoi(argv[0]);
signal(SIGINT, sighandler);
signal(SIGALRM, sighandler);
alarm(sec);
parent(sec);
return 0;
}
DEFINE_WORKLOAD(leafloop);
Annotation
- Immediate include surface: `signal.h`, `stdlib.h`, `linux/compiler.h`, `unistd.h`, `../tests.h`.
- Detected declarations: `function sighandler`, `function leaf`, `function parent`, `function leafloop`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.