From: Dave Hansen <dave.hansen@intel.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Michel Lespinasse <walken@google.com>
Subject: Re: [PATCH] Kconfig.debug: Add FRAME_POINTER anti-dependency for ARC
Date: Thu, 29 Aug 2013 08:18:07 -0700 [thread overview]
Message-ID: <521F662F.4050003@intel.com> (raw)
In-Reply-To: <1377592285-21148-1-git-send-email-vgupta@synopsys.com>
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
next prev parent reply other threads:[~2013-08-29 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:31 [PATCH] Kconfig.debug: Add FRAME_POINTER anti-dependency for ARC Vineet Gupta
2013-08-29 11:04 ` Vineet Gupta
2013-08-29 15:18 ` Dave Hansen [this message]
2013-08-30 4:25 ` Vineet Gupta
2013-08-30 7:48 ` Vineet Gupta
2013-08-30 15:20 ` Dave Hansen
2013-09-02 8:48 ` Vineet Gupta
2013-09-02 8:48 ` Vineet Gupta
2013-09-02 9:02 ` Gilad Ben-Yossef
2013-09-02 11:41 ` Vineet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521F662F.4050003@intel.com \
--to=dave.hansen@intel.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@linaro.org \
--cc=walken@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.