From: tom.zanussi@linux.intel.com
To: openembedded-core@lists.openembedded.org
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/2] oprofile: enable 'operf' perf_events mode
Date: Mon, 28 Jan 2013 14:50:54 -0600 [thread overview]
Message-ID: <cover.1359405784.git.tom.zanussi@linux.intel.com> (raw)
From: Tom Zanussi <tom.zanussi@linux.intel.com>
This patchset fixes oprofile-0.9.8 so that it finds perf_events and
configures accordingly to enable 'operf' and not just 'legacy oprofile'
I've added a new section on operf to the Yocto Tracing and Profiling Guide'
(just the wiki version for now, until I can submit a patch for the official
Guide):
https://wiki.yoctoproject.org/wiki/Tracing_and_Profiling#operf
I've tested this on real hardware (x86 crownbay), and build-tested on the
other arches (powerpc didn't build due to YOCTO bug #3717, but that's not
a regression).
The following changes since commit cfb082961a6c9ac3d65738031c4071210529cd07:
bitbake: build.py: Dump out performance data of individual tasks (2013-01-28 14:49:05 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/oprofile-operf-enable-v1
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/oprofile-operf-enable-v1
Tom Zanussi (2):
oprofile: add kernel dependency
oprofile: remove AX_KERNEL_VERSION from acinclude.m4
meta/recipes-kernel/oprofile/oprofile.inc | 2 +-
meta/recipes-kernel/oprofile/oprofile/acinclude.m4 | 19 -------------------
meta/recipes-kernel/oprofile/oprofile_0.9.8.bb | 2 ++
3 files changed, 3 insertions(+), 20 deletions(-)
--
1.7.11.4
next reply other threads:[~2013-01-28 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 20:50 tom.zanussi [this message]
2013-01-28 20:50 ` [PATCH 1/2] oprofile: add kernel dependency tom.zanussi
2013-01-28 20:50 ` [PATCH 2/2] oprofile: remove AX_KERNEL_VERSION from acinclude.m4 tom.zanussi
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.1359405784.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.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