From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: RFC: How to handle function tracing, frame pointers and -mfentry?
Date: Fri, 27 Apr 2012 14:11:55 -0700 [thread overview]
Message-ID: <4F9B0B9B.9020909@linux.intel.com> (raw)
In-Reply-To: <1335560259.28106.234.camel@gandalf.stny.rr.com>
On 04/27/2012 01:57 PM, Steven Rostedt wrote:
>>
>> Except it is the wrong thing. This is not the only user of frame
>> pointer. What I think you mean is remove the dependency in Kconfig, but
>> force the frame pointer enabled if -mfentry is not supported.
>
> You mean option 3?
>
> 3) Add frame pointers silently if gcc fails to build with gcc -pg.
>
Yes, your option 3.
-hypa
next prev parent reply other threads:[~2012-04-27 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 18:46 RFC: How to handle function tracing, frame pointers and -mfentry? Steven Rostedt
2012-04-27 19:43 ` Steven Rostedt
2012-04-27 20:27 ` Sam Ravnborg
2012-04-27 20:31 ` H. Peter Anvin
2012-04-27 20:57 ` Steven Rostedt
2012-04-27 21:11 ` H. Peter Anvin [this message]
2012-04-27 21:27 ` Steven Rostedt
2012-04-28 8:36 ` Andi Kleen
2012-04-28 8:50 ` Sam Ravnborg
2012-04-28 9:11 ` Sam Ravnborg
2012-04-28 12:16 ` Andi Kleen
2012-04-28 16:34 ` H. Peter Anvin
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=4F9B0B9B.9020909@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox