tools/perf/tests/workloads/Build

Source file repositories/reference/linux-study-clean/tools/perf/tests/workloads/Build

File Facts

System: Linux kernel
Corpus path: tools/perf/tests/workloads/Build
Extension: [no extension]
Size: 763 bytes
Lines: 24
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

# SPDX-License-Identifier: GPL-2.0

perf-test-y += noploop.o
perf-test-y += thloop.o
perf-test-y += leafloop.o
perf-test-y += sqrtloop.o
perf-test-y += brstack.o
perf-test-y += datasym.o
perf-test-y += landlock.o
perf-test-y += traploop.o
perf-test-y += inlineloop.o

ifeq ($(CONFIG_RUST_SUPPORT),y)
    perf-test-y += code_with_type.o
    perf-test-y += code_with_type.a
endif

CFLAGS_sqrtloop.o         = -g -O0 -fno-inline -U_FORTIFY_SOURCE
CFLAGS_leafloop.o         = -g -O0 -fno-inline -fno-omit-frame-pointer -U_FORTIFY_SOURCE
CFLAGS_brstack.o          = -g -O0 -fno-inline -U_FORTIFY_SOURCE
CFLAGS_datasym.o          = -g -O0 -fno-inline -U_FORTIFY_SOURCE
CFLAGS_traploop.o         = -g -O0 -fno-inline -U_FORTIFY_SOURCE
CFLAGS_inlineloop.o       = -g -O2

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.