tools/perf/tests/shell/coresight/asm_pure_loop/Makefile
Source file repositories/reference/linux-study-clean/tools/perf/tests/shell/coresight/asm_pure_loop/Makefile
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/tests/shell/coresight/asm_pure_loop/Makefile- Extension
[no extension]- Size
- 821 bytes
- Lines
- 35
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: build/configuration rule
- 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
# Carsten Haitzler <carsten.haitzler@arm.com>, 2021
include ../Makefile.miniconfig
# Binary to produce
BIN=asm_pure_loop
# Any linking/libraries needed for the binary - empty if none needed
LIB=
all: $(BIN)
$(BIN): $(BIN).S
ifdef CORESIGHT
ifeq ($(ARCH),arm64)
# Build line - this is raw asm with no libc to have an always exact binary
$(Q)$(CC) $(BIN).S -nostdlib -static -o $(BIN) $(LIB)
endif
endif
install-tests: all
ifdef CORESIGHT
ifeq ($(ARCH),arm64)
# Install the test tool in the right place
$(call QUIET_INSTALL, tests) \
$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/$(INSTDIR_SUB)/$(BIN)'; \
$(INSTALL) $(BIN) '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/$(INSTDIR_SUB)/$(BIN)/$(BIN)'
endif
endif
clean:
$(Q)$(RM) -f $(BIN)
.PHONY: all clean install-tests
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.