From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SmmUl-000541-Eq for openembedded-core@lists.openembedded.org; Thu, 05 Jul 2012 15:53:23 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q65DgJWG001127 for ; Thu, 5 Jul 2012 14:42:19 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00976-01 for ; Thu, 5 Jul 2012 14:42:16 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q65DgBkx001121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 5 Jul 2012 14:42:12 +0100 Message-ID: <1341495730.19821.14.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Thu, 05 Jul 2012 14:42:10 +0100 In-Reply-To: <1341429396.6761.18.camel@trz-ThinkPad-T420> References: <0856ecabc55e047a8d4aeb67bf213a8d11cf385a.1341338051.git.tom.zanussi@intel.com> <1341410543.3906.29.camel@ted> <1341429396.6761.18.camel@trz-ThinkPad-T420> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: [PATCH 7/9] perf: add perf-scripting MACHINE_FEATURE X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2012 13:53:23 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-07-04 at 14:16 -0500, Tom Zanussi wrote: > On Wed, 2012-07-04 at 15:02 +0100, Richard Purdie wrote: > > On Tue, 2012-07-03 at 13:10 -0500, tom.zanussi@intel.com wrote: > > > From: Tom Zanussi > > > > > > Add a new MACHINE_FEATURE named 'perf-scripting'. Adding this into > > > any machine configuration will enable perf scripting on the target, > > > which will turn on all the language bindings currently aavailable in > > > perf (Perl and Python), if perf is included in an image. > > > > > > If 'perf-scripting' isn't named as a feature (the default), all perf > > > language bindings will be disabled and unavailable. > > > > > > Signed-off-by: Tom Zanussi > > > --- > > > meta/recipes-kernel/perf/perf_3.4.bb | 11 ++++++++--- > > > 1 files changed, 8 insertions(+), 3 deletions(-) > > > > Does this make sense as a MACHINE specific feature? Wouldn't it make > > sense done on a per architecture basis for example? > > > > To me it made sense to do it as a machine-specific feature e.g. although > scripting would probably be something that all x86-64-based machines > could be assumed to easily handle and would therefore probably want, for > x86 it might not always be so clear. For example, the crownbay and > cedartrail machines might have the horsepower for scripting to make > sense on the target, while the n450 or some similarly underpowered Atom > machines, maybe not. > > So, making it a per-machine feature would allow for that kind of > flexibility... What is the implication if the machine lacks horsepower though? Isn't this something you'd only hit when trying to use specific features? I'm just not feeling this is the best way to make this decision. Cheers, Richard