1. 30 Jun, 2013 1 commit
  2. 22 Jun, 2013 1 commit
  3. 15 Jun, 2013 1 commit
  4. 09 Jun, 2013 1 commit
  5. 02 Jun, 2013 1 commit
  6. 26 May, 2013 1 commit
  7. 20 May, 2013 1 commit
  8. 12 May, 2013 1 commit
  9. 29 Apr, 2013 2 commits
    • Arnd Bergmann's avatar
      Turn off -Wmaybe-uninitialized when building with -Os · e74fc973
      Arnd Bergmann authored
      gcc-4.7 and higher add a lot of false positive warnings about
      potential uses of uninitialized warnings, but only when optimizing
      for size (-Os). This is the default when building allyesconfig,
      which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.
      In order to avoid getting a lot of patches that initialize such
      variables and accidentally hide real errors along the way, let's
      just turn off this warning on the respective gcc versions
      when building with size optimizations. The -Wmaybe-uninitialized
      option was introduced in the same gcc version (4.7) that is now
      causing the false positives, so there is no effect on older compilers.
      A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,
      we might now see /fewer/ warnings about possibly uninitialized
      warnings than with -O2, but that is still much better than seeing
      warnings known to be bogus.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
    • Linus Torvalds's avatar
      Linux 3.9 · c1be5a5b
      Linus Torvalds authored
  10. 21 Apr, 2013 1 commit
  11. 18 Apr, 2013 1 commit
    • Michal Marek's avatar
      rpm-pkg: Do not package the whole source directory · 6615d6c3
      Michal Marek authored
      The source tree can contain lots of uninteresting data like tag or
      cscope files, packaging which slows down make rpm needlessly. It can
      also break the build, if the tree contains an unrelated file named
      *.spec. The downside of this change is that new subdirectories have to
      be added to the KBUILD_ALLDIRS variable in the top-level Makefile. The
      upside is that the behavior is more predictable.
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
  12. 15 Apr, 2013 1 commit
  13. 10 Apr, 2013 1 commit
  14. 08 Apr, 2013 1 commit
  15. 31 Mar, 2013 1 commit
  16. 23 Mar, 2013 1 commit
  17. 17 Mar, 2013 1 commit
  18. 15 Mar, 2013 2 commits
    • Borislav Petkov's avatar
      perf tools: Honor parallel jobs · a50e4333
      Borislav Petkov authored
      We need to hand down parallel build options like the internal make
      --jobserver-fds one so that parallel builds can also happen when
      building perf from the toplevel directory.
      Make it so #1!
      Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Link: http://lkml.kernel.org/r/1361374353-30385-3-git-send-email-bp@alien8.de
      Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
    • Rusty Russell's avatar
      CONFIG_SYMBOL_PREFIX: cleanup. · b92021b0
      Rusty Russell authored
      We have CONFIG_SYMBOL_PREFIX, which three archs define to the string
      "_".  But Al Viro broke this in "consolidate cond_syscall and
      SYSCALL_ALIAS declarations" (in linux-next), and he's not the first to
      do so.
      Using CONFIG_SYMBOL_PREFIX is awkward, since we usually just want to
      prefix it so something.  So various places define helpers which are
      defined to nothing if CONFIG_SYMBOL_PREFIX isn't set:
      1) include/asm-generic/unistd.h defines __SYMBOL_PREFIX.
      2) include/asm-generic/vmlinux.lds.h defines VMLINUX_SYMBOL(sym)
      3) include/linux/export.h defines MODULE_SYMBOL_PREFIX.
      4) include/linux/kernel.h defines SYMBOL_PREFIX (which differs from #7)
      5) kernel/modsign_certificate.S defines ASM_SYMBOL(sym)
      6) scripts/modpost.c defines MODULE_SYMBOL_PREFIX
      7) scripts/Makefile.lib defines SYMBOL_PREFIX on the commandline if
         CONFIG_SYMBOL_PREFIX is set, so that we have a non-string version
         for pasting.
      (arch/h8300/include/asm/linkage.h defines SYMBOL_NAME(), too).
      Let's solve this properly:
      1) No more generic prefix, just CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX.
      2) Make linux/export.h usable from asm.
      4) Make everyone use them.
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
      Reviewed-by: default avatarJames Hogan <james.hogan@imgtec.com>
      Tested-by: James Hogan <james.hogan@imgtec.com> (metag)
  19. 10 Mar, 2013 1 commit
  20. 03 Mar, 2013 1 commit
  21. 22 Feb, 2013 2 commits
    • Andi Kleen's avatar
      Kbuild: Disable var tracking with CONFIG_DEBUG_INFO_REDUCED · e82c4bb8
      Andi Kleen authored
      Newer gcc enables the var-tracking pass with -g to keep track which
      registers contain which variables. This is one of the slower passes in gcc.
      With reduced debug info (aimed at objdump -S, but not using a full debugger)
      we don't need this fine grained tracking. But it was still enabled
      because -g was enabled. Disable it explicitely for DEBUG_INFO_REDUCED.
      On my 8T workstation this gives me about a 12 second gain in building
      a reasonable kernel config (2min16 vs 2min28) with DEBUG_INFO_REDUCED.
      With full DEBUG_INFO it takes 2min46
      The actual improvement in user time taken by the compiler is much higher
      (all CPU combined user time 15min5s vs 16m30 before)
      but the usual amdahl bottleneck on the linker prevents more speedup.
      It still saves some more energy and keeps cycles for other things.
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
    • James Hogan's avatar
      depmod: pass -P $CONFIG_SYMBOL_PREFIX · 8937e897
      James Hogan authored
      On architectures which have symbol prefixes, depmod emits lots of
      warnings like this:
      WARNING: $module.ko needs unknown symbol $symbol
      This is because depmod isn't being passed the -P <symbol_prefix>
      arguments to specify the symbol prefix to ignore. This option is
      included since the 3.13 release of module-init-tools.
      Update scripts/depmod.sh to take extra arguments for the symbol prefix
      (required but may be empty), and update the main Makefile to always pass
      "$(CONFIG_SYMBOL_PREFIX)" to scripts/depmod.sh.
      If the provided symbol prefix is non-empty, scripts/depmod.sh checks if
      depmod --version reports module-init-tools with a version number < 3.13
      otherwise it appends -P $SYMBOL_PREFIX to the depmod command line.
      Signed-off-by: default avatarJames Hogan <james.hogan@imgtec.com>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: linux-kbuild@vger.kernel.org
      Cc: Mike Frysinger <vapier@gentoo.org>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: uclinux-dist-devel@blackfin.uclinux.org
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
  22. 18 Feb, 2013 1 commit
  23. 08 Feb, 2013 1 commit
  24. 01 Feb, 2013 1 commit
  25. 25 Jan, 2013 3 commits
  26. 24 Jan, 2013 1 commit
  27. 22 Jan, 2013 1 commit
  28. 18 Jan, 2013 1 commit
  29. 10 Jan, 2013 1 commit
  30. 03 Jan, 2013 1 commit
  31. 22 Dec, 2012 1 commit
  32. 20 Dec, 2012 1 commit
    • David Woodhouse's avatar
      x86: Default to ARCH=x86 to avoid overriding CONFIG_64BIT · ffee0de4
      David Woodhouse authored
      It is easy to waste a bunch of time when one takes a 32-bit .config
      from a test machine and try to build it on a faster 64-bit system, and
      its existing setting of CONFIG_64BIT=n gets *changed* to match the
      build host.  Similarly, if one has an existing build tree it is easy
      to trash an entire build tree that way.
      This is because the default setting for $ARCH when discovered from
      'uname' is one of the legacy pre-x86-merge values (i386 or x86_64),
      which effectively force the setting of CONFIG_64BIT to match. We should
      default to ARCH=x86 instead, finally completing the merge that we
      started so long ago.
      This patch preserves the behaviour of the legacy ARCH settings for commands
      such as:
         make ARCH=x86_64 randconfig
         make ARCH=i386 randconfig
      ... since making the value of CONFIG_64BIT actually random in that situation
      is not desirable.
      In time, perhaps we can retire this legacy use of the old ARCH= values.
      We already have a way to override values for *any* config option, using
      $KCONFIG_ALLCONFIG, so it could be argued that we don't necessarily need
      to keep ARCH={i386,x86_64} around as a special case just for overriding
      We'd probably at least want to add a way to override config options from
      the command line ('make CONFIG_FOO=y oldconfig') before we talk about doing
      that though.
      Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      Link: http://lkml.kernel.org/r/1356040315.3198.51.camel@shinybook.infradead.org
      Signed-off-by: default avatarH. Peter Anvin <hpa@linux.intel.com>
  33. 14 Dec, 2012 1 commit
    • Josh Boyer's avatar
      MODSIGN: Add modules_sign make target · d890f510
      Josh Boyer authored
      If CONFIG_MODULE_SIG is set, and 'make modules_sign' is called then this
      patch will cause the modules to get a signature appended.  The make target
      is intended to be run after 'make modules_install', and will modify the
      modules in-place in the installed location.  It can be used to produce
      signed modules after they have been processed by distribution build
      Signed-off-by: default avatarJosh Boyer <jwboyer@redhat.com>
      Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (minor typo fix)
  34. 11 Dec, 2012 1 commit
  35. 09 Dec, 2012 1 commit