summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2024-08-20 10:45:38 +0200
committerArnd Bergmann <arnd@arndb.de>2026-07-03 20:36:07 +0200
commit25900bd99d4d10faa939a79e2fdc49c3373b51e7 (patch)
treef34fac571a8755eee40d5dbde847a9fe040bd1a8 /tools/perf/scripts/python/flamegraph.py
parent30b1c4a340892e4bb93a9596b852f5384f6605d2 (diff)
ARM: limit OABI support to StrongARM CPUs
As discussed on the mailing lists, there is no way to build OABI userspace binaries any more since gcc-4.8, and now support is also getting dropped in binutils, which will make it impossible to build pure OABI kernels at some point in the future. I found no evidence of anyone still sing OABI userspace on embedded systems that keep getting kernel updates, but there are a few desktop-class machines that date back to the 1990s using Intel StrongARM processors that were supported by old versions of Debian, Red Hat or the official Corel Netwinder distribution. Add a much stricter Kconfig dependency for both native OABI and OABI_COMPAT enabled kernels, only allowing either of them to be selected when building a kernel that targets a StrongARM based machine. Link: https://lore.kernel.org/lkml/2831c5a6-cfbf-4fe0-b51c-0396e5b0aeb7@app.fastmail.com/ Acked-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions