From: tom.zanussi@intel.com
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, sgw@linux.intel.com
Subject: [PATCH 0/3] perf-scripting/perf-tui features, v3
Date: Mon, 9 Jul 2012 12:07:07 -0500 [thread overview]
Message-ID: <cover.1341852059.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 are now turned on by default via a new variable,
PERF_FEATURES_ENABLE, which can be overridden if the default set of
perf features aren't desired (perf-scripting and perf-tui).
Because perf isn't normally enabled except in sdk builds, which
contains most of the additional packages that these features drag
in anyway e.g. Python and Perl, it shouldn't be too bothersome
to unconidtionally turn the perf features on if perf itself is
enabled. Future work will probably allow these features to be
disabled individually using PACKAGECONFIG for example.
These changes need corresponding changes made to linux-yocto and posted
separately on the yocto and linux-yocto mailing lists.
This patchset depends on the associated kernel changes posted
along with the original patchset:
http://www.mail-archive.com/yocto@yoctoproject.org/msg07279.html
http://www.mail-archive.com/yocto@yoctoproject.org/msg07286.html
Bruce Ashfield submitted a SRCREV update for the 3.4 kernel today
that you'll also need to build this.
I just started testing this, it works so far, but thought
I'd put it out there now in case there were comments before
putting too much effort into that, and possibly giving other
people a chance to try it out.
This patchset has been build-tested on the following machines:
qemuarm
The following changes since commit 5051e9837fa698e03d0a7a8a918ee7aa98409ce1:
Robert P. J. Day (1):
bitbake: usermanual: Fix missing markup
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/perf-scripting-v3
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/perf-scripting-v3
Tom Zanussi (3):
perf: add perf.inc
perf: add perf-scripting feature
perf: add perf-tui feature
meta/recipes-kernel/perf/perf.inc | 22 ++++++++++++++++++++++
meta/recipes-kernel/perf/perf_3.4.bb | 18 +++++++++++++++---
2 files changed, 37 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-kernel/perf/perf.inc
next reply other threads:[~2012-07-09 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 17:07 tom.zanussi [this message]
2012-07-09 17:07 ` [PATCH 1/3] perf: add perf.inc tom.zanussi
2012-07-09 17:07 ` [PATCH 2/3] perf: add perf-scripting feature tom.zanussi
2012-07-09 17:07 ` [PATCH 3/3] perf: add perf-tui feature tom.zanussi
2012-07-10 19:26 ` [PATCH 0/3] perf-scripting/perf-tui features, v3 Richard Purdie
2012-07-10 19:41 ` 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.1341852059.git.tom.zanussi@intel.com \
--to=tom.zanussi@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=sgw@linux.intel.com \
/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