[PATCH] x86_64: remove CONFIG_FRAME_POINTER

CONFIG_FRAME_POINTER has never worked on x86-64 because it never passed
-fno-omit-frame-pointer to the compiler, and that is the only way to get a
frame pointer on x86-64.

It also causes complications with profiling. Drop it.

Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

diff --git a/arch/x86_64/Kconfig.debug b/arch/x86_64/Kconfig.debug
index 92059a636b375b31e41602a712e184d01817d2d2..2ba7f5a059c7903b265fd40826065861ef96b333 100644 (file)
--- a/arch/x86_64/Kconfig.debug
+++ b/arch/x86_64/Kconfig.debug
@@ -30,15 +30,6 @@ config SCHEDSTATS
          application, you can say N to avoid the very slight overhead
          this adds.
 
-config FRAME_POINTER
-       bool "Compile the kernel with frame pointers"
-       help
-        Compile the kernel with frame pointers. This may help for some
-        debugging with external debuggers. Note the standard oops backtracer
-        doesn't make use of this and the x86-64 kernel doesn't ensure a
-        consistent frame pointer through inline assembly (semaphores etc.)
-        Normally you should say N.
-
 config IOMMU_DEBUG
        depends on GART_IOMMU && DEBUG_KERNEL
        bool "Enable IOMMU debugging"