1. 31 1月, 2012 1 次提交
    • D
      perf tools: Fix broken build by defining _GNU_SOURCE in Makefile · 0a84f007
      David Daney 提交于
      When building on my Debian/mips system, util/util.c fails to build
      because commit 1aed2671 (perf kvm: Do
      guest-only counting by default) indirectly includes stdio.h before the
      feature selection in util.h is done.  This prevents _GNU_SOURCE in
      util.h from enabling the declaration of getline(), from now second
      inclusion of stdio.h, and the build is broken.
      
      There is another breakage in util/evsel.c caused by include ordering,
      but I didn't fully track down the commit that caused it.
      
      The root cause of all this is an inconsistent definition of _GNU_SOURCE,
      so I move the definition into the Makefile so that it is passed to all
      invocations of the compiler and used uniformly for all system header
      files.  All other #define and #undef of _GNU_SOURCE are removed as they
      cause conflicts with the definition passed to the compiler.
      
      All the features.h definitions (_LARGEFILE64_SOURCE _FILE_OFFSET_BITS=64
      and _GNU_SOURCE) are needed by the python glue code too, so they are
      moved to BASIC_CFLAGS, and the misleading comments about BASIC_CFLAGS
      are removed.
      
      This gives me a clean build on x86_64 (fc12) and mips (Debian).
      
      Cc: David Daney <david.daney@cavium.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Joerg Roedel <joerg.roedel@amd.com>
      Cc: Namhyung Kim <namhyung.kim@lge.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/1326836461-11952-1-git-send-email-ddaney.cavm@gmail.comSigned-off-by: NDavid Daney <david.daney@cavium.com>
      Signed-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      0a84f007
  2. 13 1月, 2012 2 次提交
  3. 12 1月, 2012 3 次提交
  4. 11 1月, 2012 1 次提交
  5. 08 1月, 2012 9 次提交
  6. 07 1月, 2012 6 次提交
  7. 05 1月, 2012 2 次提交
    • S
      ktest: Add INGORE_ERRORS to ignore warnings in boot up · be405f95
      Steven Rostedt 提交于
      When testing a kernel that has warnings, ktest.pl will fail the test
      when it sees the warning. If you need to test the the kernel and want
      to ignore the errors that are produced, the option IGNORE_ERRORS has
      been added. When IGNORE_ERRORS is set to something other than 0, it will
      ignore call traces due to WARN_ON().
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      be405f95
    • S
      ktest: Still do reboot even for REBOOT_TYPE = script · 96f6a0df
      Steven Rostedt 提交于
      The REBOOT_TYPE may be either grub or script, if it is script
      it is expected that a REBOOT_SCRIPT is defined.
      
      With the SWITCH_TO_TEST which is the complement of SWITCH_TO_GOOD,
      which does basically the same thing as REBOOT_SCRIPT and but for
      both grub and script, the REBOOT_SCRIPT does not need to be mandatory
      anymore.
      
      Do not require the REBOOT_SCRIPT and always run the reboot code
      for both grub and script.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      96f6a0df
  8. 04 1月, 2012 5 次提交
  9. 02 1月, 2012 1 次提交
  10. 30 12月, 2011 1 次提交
  11. 24 12月, 2011 9 次提交