summaryrefslogtreecommitdiffstats
path: root/arch/ppc64/Kconfig
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2005-05-05 16:15:11 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-05-05 16:36:32 -0700
commit7d12e522ba13ce718b7ec32b75803dece8adb072 (patch)
tree80282ac789c1d48202a570b5828b024f39e63761 /arch/ppc64/Kconfig
parent696c2b9f97c2439e9fb299650041ec750df46865 (diff)
downloadop-kernel-dev-7d12e522ba13ce718b7ec32b75803dece8adb072.zip
op-kernel-dev-7d12e522ba13ce718b7ec32b75803dece8adb072.tar.gz
[PATCH] ppc64: remove hidden -fno-omit-frame-pointer for schedule.c
While looking at code generated by gcc4.0 I noticed some functions still had frame pointers, even after we stopped ppc64 from defining CONFIG_FRAME_POINTER. It turns out kernel/Makefile hardwires -fno-omit-frame-pointer on when compiling schedule.c. Create CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER and define it on architectures that dont require frame pointers in sched.c code. (akpm: blame me for the name) Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/ppc64/Kconfig')
-rw-r--r--arch/ppc64/Kconfig4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/ppc64/Kconfig b/arch/ppc64/Kconfig
index f5508ab..257ff66 100644
--- a/arch/ppc64/Kconfig
+++ b/arch/ppc64/Kconfig
@@ -40,6 +40,10 @@ config COMPAT
bool
default y
+config SCHED_NO_NO_OMIT_FRAME_POINTER
+ bool
+ default y
+
# We optimistically allocate largepages from the VM, so make the limit
# large enough (16MB). This badly named config option is actually
# max order + 1
OpenPOWER on IntegriCloud