tools/perf/trace/beauty/x86_arch_prctl.sh

File Facts

System

Linux kernel

Corpus path

tools/perf/trace/beauty/x86_arch_prctl.sh

Extension

.sh

Size

911 bytes

Lines

28

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
# Copyright (C) 2018, Red Hat Inc, Arnaldo Carvalho de Melo <acme@redhat.com>
# SPDX-License-Identifier: LGPL-2.1

[ $# -eq 1 ] && beauty_x86_arch_asm_uapi_dir=$1 || beauty_x86_arch_asm_uapi_dir=tools/perf/trace/beauty/arch/x86/include/uapi/asm/

prctl_arch_header=${beauty_x86_arch_asm_uapi_dir}/prctl.h

print_range () {
	idx=$1
	prefix=$2
	first_entry=$3

	printf "#define x86_arch_prctl_codes_%d_offset %s\n" $idx $first_entry
	printf "static const char *x86_arch_prctl_codes_%d[] = {\n" $idx
	regex=`printf '^[[:space:]]*#[[:space:]]*define[[:space:]]+ARCH_([[:alnum:]_]+)[[:space:]]+(%s[[:xdigit:]]+).*' ${prefix}`
	fmt="\t[%#x - ${first_entry}]= \"%s\",\n"
	grep -E -q $regex ${prctl_arch_header} && \
	(grep -E $regex ${prctl_arch_header} | \
		sed -r "s/$regex/\2 \1/g"	| \
		xargs printf "$fmt")
	printf "};\n\n"
}

print_range 1 0x1 0x1001
print_range 2 0x2 0x2001
print_range 3 0x4 0x4001

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.