Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Wed, 18 Sep 2013 14:24:38 -0400	[thread overview]
Message-ID: <cover.1379528498.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

Here are three fixes for the upcoming RCs and release. Once is a new branch, but
has zero impact on existing boards, so I've gone ahead and added it for this
upcoming release. The other two are bug fixes.

[PATCH 1/3] linux-yocto/3.8: add haswell-wc board config and branch

   Bumping the meta branch SRCREV to import the following board support:

     meta: add haswell-wc bsp for Intel Haswell Platform (Walnut Canyon CRB) scc and config files

[PATCH 2/3] linux-yocto/3.10: mips configuration changes

   Updating the 3.10 SRCREV to import the following MIPS configuration changes

      4f689aa meta: remove ftrace/ftrace-disable feature
      3058d81 mips: have the mips BSPs disable function tracing instead of ftrace
      935f43f meta: add ftrace/ftrace-function-tracer-disable feature
      0d72a03 mti-malta64: Default to support o32 and n32 userspace binaries

   The first three changes improve the ftrace disabling fragments, to allow tracepoints
   and ftrace to be enabled, while only disabling dynamic ftrace. This allows tools
   that required tracepoints (like lttng) to be built against MIPS.

   The mti-malta64 change adds n32 and o32 support to the default configuration to
   support a broader range of userspace binaries.

   [YOCTO #5215]

   Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
   Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

[PATCH 3/3] linux-yocto/3.10: fix long perf compile times

   perf's builtin-sched.c triggers extremly long build times on some
   architectures due to gcc 4.7+ var-tracking functionality.

   To fix this, we can cherry pick the 3.12 commit:

     f36f83f94 [perf sched: Move struct perf_sched definition out of cmd_sched()]

   With this change build times are reduced from 15 to 20 minutes for qemuarm to:

     real    2m19.940s
     user    1m35.438s
     sys     0m11.165s

   For kernel's that are not carrying this patch, the following can be added
   to the perf recipe to also fix the issue:

       +++ b/meta/recipes-kernel/perf/perf.bb
       @@ -68,6 +68,7 @@ EXTRA_OEMAKE = \
		       CC="${CC}" \
		       AR="${AR}" \
		       perfexecdir=${libexecdir} \
       +               EXTRA_CFLAGS="-fno-var-tracking" \
		       NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 ${SCRIPTING_DEFINES} \

Cheers,

Bruce


The following changes since commit 99b41732458871080cfa7a9bad3f8dfe03e026be:

  perf: Add LDFLAGS to allow build of old kernels without patching (2013-09-18 17:54:42 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (3):
  linux-yocto/3.8: add haswell-wc board config and branch
  linux-yocto/3.10: mips configuration changes
  linux-yocto/3.10: fix long perf compile times

 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |    6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb    |    2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |    4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb  |    2 +-
 meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   16 ++++++++--------
 meta/recipes-kernel/linux/linux-yocto_3.8.bb       |    2 +-
 6 files changed, 16 insertions(+), 16 deletions(-)

-- 
1.7.10.4



             reply	other threads:[~2013-09-18 18:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 18:24 Bruce Ashfield [this message]
2013-09-18 18:24 ` [PATCH 1/3] linux-yocto/3.8: add haswell-wc board config and branch Bruce Ashfield
2013-09-18 18:24 ` [PATCH 2/3] linux-yocto/3.10: mips configuration changes Bruce Ashfield
2013-09-18 18:24 ` [PATCH 3/3] linux-yocto/3.10: fix long perf compile times Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2020-03-22  1:18 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2019-02-09 18:37 bruce.ashfield
2019-02-06 19:50 bruce.ashfield
2019-01-21 17:26 Bruce Ashfield
2019-01-12 18:12 Bruce Ashfield
2018-04-09 15:16 Bruce Ashfield
2016-09-20 15:16 Bruce Ashfield
2016-06-06  8:15 Bruce Ashfield
2016-05-24 15:53 Bruce Ashfield
2013-11-26 17:33 Bruce Ashfield
2012-12-03 20:49 Bruce Ashfield
2012-08-27  4:49 Bruce Ashfield
2012-08-28 14:22 ` Saul Wold
2012-08-29  7:58   ` Bruce Ashfield
2012-03-05  4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-02-27 19:34 Bruce Ashfield
2012-02-28 18:41 ` Saul Wold
2012-01-04 20:12 Bruce Ashfield
2011-12-08 17:11 Bruce Ashfield
2011-09-14 18:11 Bruce Ashfield
2011-09-15 17:37 ` Saul Wold
2011-09-03  3:03 Bruce Ashfield
2011-09-05 19:26 ` Richard Purdie
2011-08-19  5:20 Bruce Ashfield
2011-08-20  5:08 ` Bruce Ashfield
2011-08-15 20:24 Bruce Ashfield
2011-08-22 22:37 ` Saul Wold
2011-05-09 18:34 Bruce Ashfield
2011-05-10 17:53 ` Saul Wold
2011-05-05  4:53 Bruce Ashfield

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.1379528498.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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