summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2024-10-01 23:59:12 +0100
committerCatalin Marinas <catalin.marinas@arm.com>2024-10-04 12:04:43 +0100
commit42155a8eb0f63f634a98ad17a85e9f2826bcff11 (patch)
tree3c41aa7aa20a6b3a334516716cb6ad1958bbde95 /tools/perf/scripts/python/stackcollapse.py
parent956573ac189066a32326245ebf5abf35b64a490f (diff)
kselftest/arm64: Always run signals tests with GCS enabled
Since it is not possible to return from the function that enabled GCS without disabling GCS it is very inconvenient to use the signal handling tests to cover GCS when GCS is not enabled by the toolchain and runtime, something that no current distribution does. Since none of the testcases do anything with stacks that would cause problems with GCS we can sidestep this issue by unconditionally enabling GCS on startup and exiting with a call to exit() rather than a return from main(). Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org> Signed-off-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20241001-arm64-gcs-v13-33-222b78d87eee@kernel.org Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions