arch/powerpc/tools/check-fpatchable-function-entry.sh
Source file repositories/reference/linux-study-clean/arch/powerpc/tools/check-fpatchable-function-entry.sh
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/tools/check-fpatchable-function-entry.sh- Extension
.sh- Size
- 917 bytes
- Lines
- 26
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- Inferred role
- Architecture Layer: arch/powerpc
- Status
- atlas-only
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
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/bash
# SPDX-License-Identifier: GPL-2.0
set -e
# To debug, uncomment the following line
# set -x
# Output from -fpatchable-function-entry can only vary on ppc64 elfv2, so this
# should not be invoked for other targets. Therefore we can pass in -m64 and
# -mabi explicitly, to take care of toolchains defaulting to other targets.
# Test whether the compile option -fpatchable-function-entry exists and
# generates appropriate code
echo "int func() { return 0; }" | \
$* -m64 -mabi=elfv2 -S -x c -O2 -fpatchable-function-entry=2 - -o - 2> /dev/null | \
grep -q "__patchable_function_entries"
# Test whether nops are generated after the local entry point
echo "int x; int func() { return x; }" | \
$* -m64 -mabi=elfv2 -S -x c -O2 -fpatchable-function-entry=2 - -o - 2> /dev/null | \
awk 'BEGIN { RS = ";" } /\.localentry.*nop.*\n[[:space:]]*nop/ { print $0 }' | \
grep -q "func:"
exit 0
Annotation
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.