On 08/27/2013 01:31 AM, Vineet Gupta wrote: > Frame pointer on ARC doesn't serve the conventional purpose of stack > unwinding due to the typical way ABI designates it's usage. > Thus it's explicit usage on ARC is discouraged (gcc is free to use it, > for some tricky stack frames even if -fomit-frame-pointer) ... > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 1501aa5..c971f3a 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -908,7 +908,7 @@ config LOCKDEP > bool > depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT > && LOCKDEP_SUPPORT > select STACKTRACE > - select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && > !MICROBLAZE > + select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && > !MICROBLAZE && !ARC > select KALLSYMS > select KALLSYMS_ALL
I assume you're sending this my way since getmaintainer.pl has me tagged I moved a bunch of code in there. :) The Kconfig.debug stuff has no real maintainer. It would probably be OK if you just stick this in your architecture's next git pull request. Although, it would be nice if someone, at some point, actually abstracted that out so that the individual architectures could take care of this without editing the main files: # Kconfig.debug: config ARCH_FRAME_POINTER_UNAVAILABLE def_bool y ... select FRAME_POINTER if !ARCH_FRAME_POINTER_UNAVAILABLE # arch/.../Kconfig select ARCH_FRAME_POINTER_UNAVAILABLE -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/