All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] linux-yocto/3.4: make uprobes select perf events
Date: Fri, 14 Sep 2012 09:58:19 +0100	[thread overview]
Message-ID: <1347613099.9456.8.camel@ted> (raw)
In-Reply-To: <5f0da99ea0b685191dc7b8fd5fd633783ed92664.1347597967.git.bruce.ashfield@windriver.com>

On Fri, 2012-09-14 at 00:57 -0400, Bruce Ashfield wrote:
> uprobes depends on functionality provided by perf events. After
> uprobes was enabled in the standard kernel the mpc8315 board showed
> link errors due to missing perf event functions.
> 
> This problem isn't isolated to the board or powerpc arch, but all
> other boards have PERF_EVENTS enabled. To fix this, we make UPROBE_EVENT
> select PERF_EVENTS, and any new boards will be protected from the
> same failure.
> 
> We also update the configuration fragments since CONFIG_UPROBES depends on
> CONFIG_PERF_EVENTS being set, so PERF_EVENTS needs to be added whenever
> uprobes are enabled.
> 
> [YOCTO #3111]
> 
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |    6 +++---
>  meta/recipes-kernel/linux/linux-yocto_3.4.bb    |   14 +++++++-------
>  2 files changed, 10 insertions(+), 10 deletions(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2012-09-14  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  4:57 [PATCH 0/1] linux-yocto/3.4: make uprobes select perf events Bruce Ashfield
2012-09-14  4:57 ` [PATCH 1/1] " Bruce Ashfield
2012-09-14  8:58   ` Richard Purdie [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=1347613099.9456.8.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.