mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>
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 16:57:39 -0400	[thread overview]
Message-ID: <1335560259.28106.234.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4F9B020B.9050205@linux.intel.com>

On Fri, 2012-04-27 at 13:31 -0700, H. Peter Anvin wrote:
> On 04/27/2012 01:27 PM, Sam Ravnborg wrote:
> >>
> >> My question is, how do I remove the dependency in kconfig based on the
> >> compiler?
> > 
> > Allow the user to select one of:
> > 1) function tracer
> > 2) frame pointer
> > 3) none of the above
> > 
> > This should be trivial to do in Kconfig language.
> > 
> > If "function tracer" is selected then use -mfentry if supported,
> > with a fallback to frame pointers.
> > 
> > This looks simple IMO and should be easy to implement too.
> > 
> 
> 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.

Which I should have added, relies on the same thing as option 2:

2) Remove the select entirely.


-- Steve



  reply	other threads:[~2012-04-27 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 18:46 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 [this message]
2012-04-27 21:11       ` H. Peter Anvin
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=1335560259.28106.234.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mmarek@suse.cz \
    --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

all inboxes | Powered by JetHome®