scripts/Makefile.vdsoinst

File Facts

System

Linux kernel

Corpus path

scripts/Makefile.vdsoinst

Extension

.vdsoinst

Size

1060 bytes

Lines

46

Domain

Support Tooling And Documentation

Bucket

scripts

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-only
# ==========================================================================
# Install unstripped copies of vDSO
# ==========================================================================

PHONY := __default
__default:
	@:

include $(srctree)/scripts/Kbuild.include

install-dir := $(MODLIB)/vdso

define gen_install_rules

dest := $(install-dir)/$$(patsubst %.dbg,%,$$(notdir $(1)))

__default: $$(dest)
$$(dest): $(1) FORCE
	$$(call cmd,install)

build-id-file := $$(shell $(READELF) -n $(1) 2>/dev/null | sed -n 's@^.*Build ID: \(..\)\(.*\)@\1/\2@p')

ifneq ($$(build-id-file),)
link := $(install-dir)/.build-id/$$(build-id-file).debug

__default: $$(link)
$$(link): $$(dest) FORCE
	$$(call cmd,symlink)
endif

endef

$(foreach x, $(sort $(INSTALL_FILES)), $(eval $(call gen_install_rules,$(x))))

quiet_cmd_install = INSTALL $@
      cmd_install = mkdir -p $(dir $@); cp $< $@

quiet_cmd_symlink = SYMLINK $@
      cmd_symlink = mkdir -p $(dir $@); ln -sf --relative $< $@

PHONY += FORCE
FORCE:

.PHONY: $(PHONY)

Annotation

• Atlas domain: Support Tooling And Documentation / scripts.
• 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.