Openembedded Core Discussions
 help / color / mirror / Atom feed
From: tom.zanussi@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] perf: enable Perl and Python bindings, and perf TUI
Date: Tue,  3 Jul 2012 13:10:33 -0500	[thread overview]
Message-ID: <cover.1341338051.git.tom.zanussi@intel.com> (raw)

From: Tom Zanussi <tom.zanussi@intel.com>

This patchset enables the Perl and Python bindings for perf, as well as
the perf TUI (text-based UI).

These can be separately enabled on a machine basis by adding
'perf-scripting' and/or 'perf-tui' to the machine's MACHINE_FEATURES.
The default is to completely disable all scripting and TUI features.

There are also a couple patches that fix other problems noticed along
the way.

These changes need corresponding changes made to linux-yocto and posted
separately on the yocto and linux-yocto mailing lists.

This patchset has been build- and run-tested on the following machines:

qemux86
qemux86-64
qemuarm
sugarbay
crownbay

The following changes since commit 644ad4bf1e30fcee4b9d5abb819046d1f2193d27:
  Scott Rifenbark (1):
        documentation/bsp-guide/bsp.xml: Yocto term paring

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib.git tzanussi/perf-scripting
  http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/perf-scripting

Tom Zanussi (9):
  perl: keep original libperl location
  perl: add @STAGINGDIR@ for config.sh substitions
  perl: use @STAGINGDIR@ in config.sh
  perf: enable Python bindings
  perf: enable Perl binding
  perf: add libexec/perf-core and contents
  perf: add perf-scripting MACHINE_FEATURE
  qemumachines: make MACHINE_FEATURES append follow qemu.inc include
  perf: add perf-tui MACHINE_FEATURE

 meta/conf/machine/qemux86-64.conf                |    4 +-
 meta/conf/machine/qemux86.conf                   |    4 +-
 meta/recipes-devtools/perl/perl-5.14.2/config.sh |    2 +-
 meta/recipes-devtools/perl/perl_5.14.2.bb        |    4 ++-
 meta/recipes-kernel/perf/perf_3.4.bb             |   36 ++++++++++++++++++++--
 5 files changed, 41 insertions(+), 9 deletions(-)




             reply	other threads:[~2012-07-03 18:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 18:10 tom.zanussi [this message]
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
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=cover.1341338051.git.tom.zanussi@intel.com \
    --to=tom.zanussi@intel.com \
    --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