From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/9] perf: add perf-scripting MACHINE_FEATURE
Date: Wed, 04 Jul 2012 15:02:23 +0100 [thread overview]
Message-ID: <1341410543.3906.29.camel@ted> (raw)
In-Reply-To: <0856ecabc55e047a8d4aeb67bf213a8d11cf385a.1341338051.git.tom.zanussi@intel.com>
On Tue, 2012-07-03 at 13:10 -0500, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> 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 <tom.zanussi@intel.com>
> ---
> 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?
Cheers,
Richard
next prev parent reply other threads:[~2012-07-04 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 18:10 [PATCH 0/9] perf: enable Perl and Python bindings, and perf TUI tom.zanussi
2012-07-03 18:10 ` [PATCH 1/9] perl: keep original libperl location tom.zanussi
2012-07-03 18:10 ` [PATCH 2/9] perl: add @STAGINGDIR@ for config.sh substitions tom.zanussi
2012-07-03 18:10 ` [PATCH 3/9] perl: use @STAGINGDIR@ in config.sh tom.zanussi
2012-07-03 18:10 ` [PATCH 4/9] perf: enable Python bindings tom.zanussi
2012-07-03 18:10 ` [PATCH 5/9] perf: enable Perl binding tom.zanussi
2012-07-03 18:10 ` [PATCH 6/9] perf: add libexec/perf-core and contents tom.zanussi
2012-07-03 18:10 ` [PATCH 7/9] perf: add perf-scripting MACHINE_FEATURE tom.zanussi
2012-07-04 14:02 ` Richard Purdie [this message]
2012-07-04 19:16 ` Tom Zanussi
2012-07-05 13:42 ` Richard Purdie
2012-07-05 13:54 ` Tom Zanussi
2012-07-03 18:10 ` [PATCH 8/9] qemumachines: make MACHINE_FEATURES append follow qemu.inc include tom.zanussi
2012-07-03 18:10 ` [PATCH 9/9] perf: add perf-tui MACHINE_FEATURE tom.zanussi
2012-07-05 17:56 ` [PATCH 0/9] perf: enable Perl and Python bindings, and perf TUI Saul Wold
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=1341410543.3906.29.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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