Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754590Ab2HIDqA (ORCPT ); Wed, 8 Aug 2012 23:46:00 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:63310 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753893Ab2HIDp7 (ORCPT ); Wed, 8 Aug 2012 23:45:59 -0400 MIME-Version: 1.0 In-Reply-To: <1344430148.6935.17.camel@gandalf.stny.rr.com> References: <20120807193845.146666357@goodmis.org> <20120807194059.773895870@goodmis.org> <5021EC6B.7020605@hitachi.com> <1344430148.6935.17.camel@gandalf.stny.rr.com> From: Linus Torvalds Date: Thu, 9 Aug 2012 06:45:37 +0300 X-Google-Sender-Auth: JGOU2vL6ttVmsUkAlXql-8Cdlps Message-ID: Subject: Re: [RFC PATCH 3/4] ftrace: Do not test frame pointers if -mfentry is used To: Steven Rostedt , Michal Marek Cc: Masami Hiramatsu , linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton , Thomas Gleixner , Frederic Weisbecker , Andi Kleen Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1137 Lines: 24 On Wed, Aug 8, 2012 at 3:49 PM, Steven Rostedt wrote: > > No, CONFIG_HAVE_FENTRY just means fentry is supported, it does not mean > that it is being used. It only gets used if CC_USING_FENTRY is set, > which is set by the Makefile at time of compile. Btw, it might be lovely to consider the concept of "Kconfig variables set by shell-scripts". We currently have a metric sh*t-ton of Makefile magic for testing various things like this, and integrating it into Kconfig might be a good idea. That way you would be able to use the Kconfig logic on these things. Kconfig already has the "option env=XYZ" syntax for importing values from the environment variables. Extending it to some kind of "option shell=xyz" would allow for more complex interactions like this (imagine testing compiler options and version dependencies in the Kconfig files instead of the Makefiles)? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/