[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F9B020B.9050205@linux.intel.com>
Date: Fri, 27 Apr 2012 13:31:07 -0700
From: "H. Peter Anvin" <hpa@...ux.intel.com>
To: Sam Ravnborg <sam@...nborg.org>
CC: Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
Michal Marek <mmarek@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: RFC: How to handle function tracing, frame pointers and -mfentry?
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.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists