summaryrefslogtreecommitdiffstats
path: root/fs/open.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2011-06-10 14:12:21 +0000
committerArnd Bergmann <arnd@arndb.de>2011-10-01 21:08:43 +0200
commit89bace652cbfb78a2fd830025f8ea048d6eb3657 (patch)
tree6bd41b49614a50bd7f4bd8743da9006b926dce04 /fs/open.c
parent9934ebb8ffb1554ad76764b6e71767378d051329 (diff)
downloadop-kernel-dev-89bace652cbfb78a2fd830025f8ea048d6eb3657.zip
op-kernel-dev-89bace652cbfb78a2fd830025f8ea048d6eb3657.tar.gz
ARM: always use ARM_UNWIND for thumb2 kernels
Thumb2 kernels cannot be built with frame pointers, but can use the ARM_UNWIND feature for unwinding instead. This makes sure that all features that rely on unwinding includeing CONFIG_LATENCYTOP and FAULT_INJECTION_STACKTRACE_FILTER do not enable frame pointers when the unwinder is already selected, and we always build with the unwinder when we want a thumb2 kernel, to make sure we do not get the frame pointers instead. A different option would be to redefine the CONFIG_FRAME_POINTERS option on ARM to mean builing with either frame pointers or the unwinder, and then select which one to use based on the CPU architecture or another user option. That would still allow building thumb2 kernels without the unwinder but would also be more confusing. Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'fs/open.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud