Commit ae1e9130 authored by Ingo Molnar's avatar Ingo Molnar

sched: rename SCHED_NO_NO_OMIT_FRAME_POINTER => SCHED_OMIT_FRAME_POINTER

Impact: cleanup, change .config option name

We had this ugly config name for a long time for hysteric raisons.
Rename it to a saner name.

We still cannot get rid of it completely, until /proc/<pid>/stack
usage replaces WCHAN usage for good.

We'll be able to do that in the v2.6.29/v2.6.30 timeframe.
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent 6d21cd62
...@@ -99,7 +99,7 @@ config GENERIC_IOMAP ...@@ -99,7 +99,7 @@ config GENERIC_IOMAP
bool bool
default y default y
config SCHED_NO_NO_OMIT_FRAME_POINTER config SCHED_OMIT_FRAME_POINTER
bool bool
default y default y
......
...@@ -273,7 +273,7 @@ config GENERIC_CALIBRATE_DELAY ...@@ -273,7 +273,7 @@ config GENERIC_CALIBRATE_DELAY
bool bool
default y default y
config SCHED_NO_NO_OMIT_FRAME_POINTER config SCHED_OMIT_FRAME_POINTER
bool bool
default y default y
......
...@@ -653,7 +653,7 @@ config GENERIC_CMOS_UPDATE ...@@ -653,7 +653,7 @@ config GENERIC_CMOS_UPDATE
bool bool
default y default y
config SCHED_NO_NO_OMIT_FRAME_POINTER config SCHED_OMIT_FRAME_POINTER
bool bool
default y default y
......
...@@ -141,7 +141,7 @@ config GENERIC_NVRAM ...@@ -141,7 +141,7 @@ config GENERIC_NVRAM
bool bool
default y if PPC32 default y if PPC32
config SCHED_NO_NO_OMIT_FRAME_POINTER config SCHED_OMIT_FRAME_POINTER
bool bool
default y default y
......
...@@ -364,7 +364,7 @@ config X86_RDC321X ...@@ -364,7 +364,7 @@ config X86_RDC321X
as R-8610-(G). as R-8610-(G).
If you don't have one of these chips, you should say N here. If you don't have one of these chips, you should say N here.
config SCHED_NO_NO_OMIT_FRAME_POINTER config SCHED_OMIT_FRAME_POINTER
def_bool y def_bool y
prompt "Single-depth WCHAN output" prompt "Single-depth WCHAN output"
depends on X86 depends on X86
......
...@@ -23,7 +23,7 @@ ...@@ -23,7 +23,7 @@
*/ */
#if defined(CONFIG_FRAME_POINTER) || \ #if defined(CONFIG_FRAME_POINTER) || \
!defined(CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER) !defined(CONFIG_SCHED_OMIT_FRAME_POINTER)
#define M32R_PUSH_FP " push fp\n" #define M32R_PUSH_FP " push fp\n"
#define M32R_POP_FP " pop fp\n" #define M32R_POP_FP " pop fp\n"
#else #else
......
...@@ -91,7 +91,7 @@ obj-$(CONFIG_FUNCTION_TRACER) += trace/ ...@@ -91,7 +91,7 @@ obj-$(CONFIG_FUNCTION_TRACER) += trace/
obj-$(CONFIG_TRACING) += trace/ obj-$(CONFIG_TRACING) += trace/
obj-$(CONFIG_SMP) += sched_cpupri.o obj-$(CONFIG_SMP) += sched_cpupri.o
ifneq ($(CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER),y) ifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y)
# According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is # According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is
# needed for x86 only. Why this used to be enabled for all architectures is beyond # needed for x86 only. Why this used to be enabled for all architectures is beyond
# me. I suspect most platforms don't need this, but until we know that for sure # me. I suspect most platforms don't need this, but until we know that for sure
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment