diff options
| author | Jose Fernandez (Anthropic) <jose.fernandez@linux.dev> | 2026-06-09 05:19:27 +0000 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2026-07-22 20:50:52 +0000 |
| commit | 9315e22b0c0a5be708798c03dc8f27549667e475 (patch) | |
| tree | e90ed604e5945351ea54410d46f29e9adc9280e4 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 123b4fc0f8576ac29b965cfc362630f51fa0fe7e (diff) | |
arm64: ftrace: allow DIRECT_CALLS without CALL_OPS
Drop the CALL_OPS requirement from the HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
select. Configurations that keep CALL_OPS (!CFI clang builds, and GCC builds
without CC_OPTIMIZE_FOR_SIZE) are unchanged. CALL_OPS-less configurations
take the ftrace_caller ops-dispatch path for out-of-range direct calls,
trading the per-callsite fast path for working BPF trampolines; in-range
attachments still branch directly with no overhead. GCC -Os builds also gain
DIRECT_CALLS as a side effect. That is intended: s390 and loongarch already
ship DIRECT_CALLS without any per-callsite fast path.
Assisted-by: Claude:unspecified
Signed-off-by: Jose Fernandez (Anthropic) <jose.fernandez@linux.dev>
Acked-by: Xu Kuohai <xukuohai@huawei.com>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Tested-by: Clayton Craft <craftyguy@postmarketos.org>
Reviewed-by: Puranjay Mohan <puranjay@kernel.org>
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
