Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] perf: add libunwind support
Date: Tue, 9 Sep 2014 14:27:20 +0800	[thread overview]
Message-ID: <540E9DC8.9090708@windriver.com> (raw)
In-Reply-To: <d2d05abe9ec5edc07e7f064ac52748ea87847c3f.1409301362.git.Chong.Lu@windriver.com>

ping

On 08/29/2014 04:38 PM, Chong Lu wrote:
> Add a new feature named 'perf-libunwind'. Adding this support to perf allows it
> to do stack traces on ARM - thumb2 and MIPS targets. PERF_FEATURES variable in
> perf-features.inc will enable the perf-libunwind.
>
> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
> ---
>   meta/recipes-kernel/perf/perf-features.inc | 2 +-
>   meta/recipes-kernel/perf/perf.bb           | 5 ++++-
>   2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-kernel/perf/perf-features.inc b/meta/recipes-kernel/perf/perf-features.inc
> index b8859ab..2dbbb47 100644
> --- a/meta/recipes-kernel/perf/perf-features.inc
> +++ b/meta/recipes-kernel/perf/perf-features.inc
> @@ -1,4 +1,4 @@
> -PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui"
> +PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui perf-libunwind"
>   
>   def perf_feature_enabled(feature, trueval, falseval, d):
>       """
> diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
> index bfd210c..ab94a05 100644
> --- a/meta/recipes-kernel/perf/perf.bb
> +++ b/meta/recipes-kernel/perf/perf.bb
> @@ -20,6 +20,7 @@ BUILDPERF_libc-uclibc = "no"
>   # to cover a wide range of kernel we add both dependencies
>   TUI_DEPENDS = "${@perf_feature_enabled('perf-tui', 'libnewt slang', '',d)}"
>   SCRIPTING_DEPENDS = "${@perf_feature_enabled('perf-scripting', 'perl python', '',d)}"
> +LIBUNWIND_DEPENDS = "${@perf_feature_enabled('perf-libunwind', 'libunwind', '',d)}"
>   
>   DEPENDS = "virtual/kernel \
>       virtual/${MLPREFIX}libc \
> @@ -27,6 +28,7 @@ DEPENDS = "virtual/kernel \
>       ${MLPREFIX}binutils \
>       ${TUI_DEPENDS} \
>       ${SCRIPTING_DEPENDS} \
> +    ${LIBUNWIND_DEPENDS} \
>       bison flex \
>   "
>   
> @@ -62,6 +64,7 @@ B = "${WORKDIR}/${BPN}-${PV}"
>   
>   SCRIPTING_DEFINES = "${@perf_feature_enabled('perf-scripting', '', 'NO_LIBPERL=1 NO_LIBPYTHON=1',d)}"
>   TUI_DEFINES = "${@perf_feature_enabled('perf-tui', '', 'NO_NEWT=1',d)}"
> +LIBUNWIND_DEFINES = "${@perf_feature_enabled('perf-libunwind', '', 'NO_LIBUNWIND=1',d)}"
>   
>   # The LDFLAGS is required or some old kernels fails due missing
>   # symbols and this is preferred than requiring patches to every old
> @@ -76,7 +79,7 @@ EXTRA_OEMAKE = '\
>       CC="${CC}" \
>       AR="${AR}" \
>       perfexecdir=${libexecdir} \
> -    NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 NO_LIBUNWIND=1 ${SCRIPTING_DEFINES} \
> +    NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 ${LIBUNWIND_DEFINES} ${SCRIPTING_DEFINES} \
>   '
>   
>   EXTRA_OEMAKE += "\



      reply	other threads:[~2014-09-09  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:38 [PATCH 0/2] perf: add libunwind support Chong Lu
2014-08-29  8:38 ` [PATCH 1/2] libunwind: add recipes Chong Lu
2014-08-29  9:14   ` Chong Lu
2014-09-09  6:26   ` Chong Lu
2014-08-29  8:38 ` [PATCH 2/2] perf: add libunwind support Chong Lu
2014-09-09  6:27   ` Chong Lu [this message]

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=540E9DC8.9090708@windriver.com \
    --to=chong.lu@windriver.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