1. 15 6月, 2011 1 次提交
  2. 13 6月, 2011 8 次提交
    • S
      ktest: Allow initrd processing without modules defined · db05cfef
      Steven Rostedt 提交于
      When a config is set with CONFIG_MODULES=n, it does not mean that the
      kernel does not need an initrd to boot. For systems that depend on LVM
      and such, an initrd must run first.
      
      If POST_INSTALL is defined, then run the post install regardless if
      modules are needed or not.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      db05cfef
    • S
      ktest: Have LOG_FILE evaluate options as well · 23715c3c
      Steven Rostedt 提交于
      The LOG_FILE variable needs to evaluate the $ options as well.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      23715c3c
    • S
      ktest: Have wait on stdio honor bug timeout · ecaf8e52
      Steven Rostedt 提交于
      After a bug is found, the STOP_AFTER_FAILURE timeout is used to
      determine how much output should be printed before breaking out
      of the monitor loop. This is to get things like call traces and
      enough infromation about the bug to help determine what caused it.
      
      The STOP_AFTER_FAILURE is usually much shorter than the TIMEOUT
      that is used to determine when to quit after no more stdio is given.
      
      But since the stdio read uses a wait on I/O, the STOP_AFTER_FAILURE is
      only checked after we get something from I/O. But if the I/O does
      not return any more data, we wait the TIMEOUT period instead, even
      though we already triggered a bug report.
      
      The wait on I/O should honor the STOP_AFTER_FAILURE time if a bug has
      been found.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      ecaf8e52
    • S
      ktest: Implement our own force min config · fcb3f16a
      Steven Rostedt 提交于
      Using the build KCONFIG_ALLCONFIG environment variable to force
      the min config may not always work properly. Since ktest is
      written in perl, it is trivial to read and replace the current
      config with the configs specified by the min config.
      
      Now the min config (and add configs) are read by perl and before
      a make is done, these configs in the .config file are replaced
      by the version in the min config.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      fcb3f16a
    • S
      ktest: Add TEST_NAME option · 9064af52
      Steven Rostedt 提交于
      Searching through several tests, it gets confusing which test result
      is for which test. By adding the TEST_NAME option, the user can tell
      which test result belongs to which test.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      9064af52
    • S
      ktest: Add CONFIG_BISECT_GOOD option · 30f75da5
      Steven Rostedt 提交于
      Currently the config_bisect compares the min config with the
      CONFIG_BISECT config. There may be another config that we know
      is good that we want to ignore configs on. By passing in this
      config it will ignore the options that are set in the good config.
      
      Note: This only ignores the config, it does not (yet) handle
      options that are different between the two configs. If the good
      config has "SLAB" set and the bad config has "SLUB" it will not
      find the bug if the bug had to do with changing these two options.
      
      This is something that I intend to implement in the future.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      30f75da5
    • S
      ktest: Add detection of triple faults · f1a5b962
      Steven Rostedt 提交于
      When a triple fault happens in a test, no call trace nor panic
      is displayed. Instead, the system reboots to the good kernel.
      Since the good kernel may display a boot prompt that matches the
      success string, ktest may think that the test succeeded, when it
      did not.
      
      Detecting triple faults is tricky because it is hard to generalize
      what a reboot looks like. The best that we can come up with for now
      is to examine the Linux banner. If we detect that the Linux banner
      matches the test we want to test, then look to see if we hit another
      Linux banner with a different kernel is booted. This can be assumed
      to be a triple fault.
      
      We can't just check for two Linux banners because things like
      early printk may cause the Linux banner to be displayed twice. Checking
      for different kernel versions should be the safe bet.
      
      If this for some reason detects a false triple boot. A new ktest
      config option is also created:
      
       DETECT_TRIPLE_FAULT
      
      This can be set to 0 to disable this checking.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      f1a5b962
    • S
      ktest: Notify reason to break out of monitoring boot · cd4f1d53
      Steven Rostedt 提交于
      Different timeouts can cause the ktest monitor to break out of the
      loop. It becomes annoying that one does not know the reason why
      it exited the monitor loop. Display the cause of the reason why
      the loop was exited.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      cd4f1d53
  3. 02 6月, 2011 3 次提交
  4. 30 5月, 2011 1 次提交
  5. 28 5月, 2011 5 次提交
  6. 26 5月, 2011 3 次提交
    • A
      perf tools: Fix build on older systems · 75911c9b
      Arnaldo Carvalho de Melo 提交于
      Where /usr/include/linux/const.h is not present, e.g. RHEL5.
      Reported-by: NSrikar Dronamraju <srikar@linux.vnet.ibm.com>
      Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Stephane Eranian <eranian@google.com>
      Cc: Tom Zanussi <tzanussi@gmail.com>
      Link: http://lkml.kernel.org/n/tip-ypcw2mu0w7dl1rrc6ncz3pee@git.kernel.orgSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      75911c9b
    • A
      perf symbols: Handle /proc/sys/kernel/kptr_restrict · ec80fde7
      Arnaldo Carvalho de Melo 提交于
      Perf uses /proc/modules to figure out where kernel modules are loaded.
      
      With the advent of kptr_restrict, non root users get zeroes for all module
      start addresses.
      
      So check if kptr_restrict is non zero and don't generate the syntethic
      PERF_RECORD_MMAP events for them.
      
      Warn the user about it in perf record and in perf report.
      
      In perf report the reference relocation symbol being zero means that
      kptr_restrict was set, thus /proc/kallsyms has only zeroed addresses, so don't
      use it to fixup symbol addresses when using a valid kallsyms (in the buildid
      cache) or vmlinux (in the vmlinux path) build-id located automatically or
      specified by the user.
      
      Provide an explanation about it in 'perf report' if kernel samples were taken,
      checking if a suitable vmlinux or kallsyms was found/specified.
      
      Restricted /proc/kallsyms don't go to the buildid cache anymore.
      
      Example:
      
       [acme@emilia ~]$ perf record -F 100000 sleep 1
      
       WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted, check
       /proc/sys/kernel/kptr_restrict.
      
       Samples in kernel functions may not be resolved if a suitable vmlinux file is
       not found in the buildid cache or in the vmlinux path.
      
       Samples in kernel modules won't be resolved at all.
      
       If some relocation was applied (e.g. kexec) symbols may be misresolved even
       with a suitable vmlinux or kallsyms file.
      
       [ perf record: Woken up 1 times to write data ]
       [ perf record: Captured and wrote 0.005 MB perf.data (~231 samples) ]
       [acme@emilia ~]$
      
       [acme@emilia ~]$ perf report --stdio
       Kernel address maps (/proc/{kallsyms,modules}) were restricted,
       check /proc/sys/kernel/kptr_restrict before running 'perf record'.
      
       If some relocation was applied (e.g. kexec) symbols may be misresolved.
      
       Samples in kernel modules can't be resolved as well.
      
       # Events: 13  cycles
       #
       # Overhead  Command      Shared Object                 Symbol
       # ........  .......  .................  .....................
       #
          20.24%    sleep  [kernel.kallsyms]  [k] page_fault
          20.04%    sleep  [kernel.kallsyms]  [k] filemap_fault
          19.78%    sleep  [kernel.kallsyms]  [k] __lru_cache_add
          19.69%    sleep  ld-2.12.so         [.] memcpy
          14.71%    sleep  [kernel.kallsyms]  [k] dput
           4.70%    sleep  [kernel.kallsyms]  [k] flush_signal_handlers
           0.73%    sleep  [kernel.kallsyms]  [k] perf_event_comm
           0.11%    sleep  [kernel.kallsyms]  [k] native_write_msr_safe
      
       #
       # (For a higher level overview, try: perf report --sort comm,dso)
       #
       [acme@emilia ~]$
      
      This is because it found a suitable vmlinux (build-id checked) in
      /lib/modules/2.6.39-rc7+/build/vmlinux (use -v in perf report to see the long
      file name).
      
      If we remove that file from the vmlinux path:
      
       [root@emilia ~]# mv /lib/modules/2.6.39-rc7+/build/vmlinux \
      		     /lib/modules/2.6.39-rc7+/build/vmlinux.OFF
       [acme@emilia ~]$ perf report --stdio
       [kernel.kallsyms] with build id 57298cdbe0131f6871667ec0eaab4804dcf6f562
       not found, continuing without symbols
      
       Kernel address maps (/proc/{kallsyms,modules}) were restricted, check
       /proc/sys/kernel/kptr_restrict before running 'perf record'.
      
       As no suitable kallsyms nor vmlinux was found, kernel samples can't be
       resolved.
      
       Samples in kernel modules can't be resolved as well.
      
       # Events: 13  cycles
       #
       # Overhead  Command      Shared Object  Symbol
       # ........  .......  .................  ......
       #
          80.31%    sleep  [kernel.kallsyms]  [k] 0xffffffff8103425a
          19.69%    sleep  ld-2.12.so         [.] memcpy
      
       #
       # (For a higher level overview, try: perf report --sort comm,dso)
       #
       [acme@emilia ~]$
      Reported-by: NStephane Eranian <eranian@google.com>
      Suggested-by: NDavid Miller <davem@davemloft.net>
      Cc: Dave Jones <davej@redhat.com>
      Cc: David Miller <davem@davemloft.net>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Kees Cook <kees.cook@canonical.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Stephane Eranian <eranian@google.com>
      Cc: Tom Zanussi <tzanussi@gmail.com>
      Link: http://lkml.kernel.org/n/tip-mt512joaxxbhhp1odop04yit@git.kernel.orgSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      ec80fde7
    • J
      perf: Remove duplicate headers · ea7659fb
      Jesper Juhl 提交于
      Signed-off-by: NJesper Juhl <jj@chaosbits.net>
      Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
      Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
      Cc: trivial@kernel.org
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Paul Mackerras <paulus@samba.org>
      Link: http://lkml.kernel.org/r/alpine.LNX.2.00.1105261011290.17400@swampdragon.chaosbits.netSigned-off-by: NIngo Molnar <mingo@elte.hu>
      ea7659fb
  7. 24 5月, 2011 1 次提交
  8. 23 5月, 2011 2 次提交
  9. 22 5月, 2011 6 次提交
  10. 21 5月, 2011 3 次提交
    • L
      sanitize <linux/prefetch.h> usage · 268bb0ce
      Linus Torvalds 提交于
      Commit e66eed65 ("list: remove prefetching from regular list
      iterators") removed the include of prefetch.h from list.h, which
      uncovered several cases that had apparently relied on that rather
      obscure header file dependency.
      
      So this fixes things up a bit, using
      
         grep -L linux/prefetch.h $(git grep -l '[^a-z_]prefetchw*(' -- '*.[ch]')
         grep -L 'prefetchw*(' $(git grep -l 'linux/prefetch.h' -- '*.[ch]')
      
      to guide us in finding files that either need <linux/prefetch.h>
      inclusion, or have it despite not needing it.
      
      There are more of them around (mostly network drivers), but this gets
      many core ones.
      Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      268bb0ce
    • S
      ktest: Allow options to be used by other options · 2a62512b
      Steven Rostedt 提交于
      There are cases where one ktest option may be used within another
      ktest option. Allow them to be reused just like config variables
      but there are evaluated at time of test not config processing time.
      
      Thus having something like:
      
      MAKE_CMD = make ARCH=${ARCH}
      
      TEST_START
      ARCH = powerpc
      
      TEST_START
      ARCH = arm
      
      Will have the arch defined for each test iteration.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      2a62512b
    • S
      ktest: Create variables for the ktest config files · 77d942ce
      Steven Rostedt 提交于
      I found that I constantly reuse information for each test case.
      It would be nice to just define a variable to reuse.
      
      For example I may have:
      
      TEST_START
      [...]
      TEST = ssh root@mybox /path/to/my/script
      
      TEST_START
      [...]
      TEST = ssh root@mybox /path/to/my/script
      
      [etc]
      
      The issue is, I may wont to change that script or one of the other
      fields. Then I need to update each line individually.
      
      With the addition of config variables (variables only used during parsing
      the config) we can simplify the config files. These variables can
      also be defined multiple times and each time the new value will
      overwrite the old value.
      
      The convention to use a config variable over a ktest option is to use :=
      instead of =.
      
      Now we could do:
      
      USER := root
      TARGET := mybox
      TEST_SCRIPT := /path/to/my/script
      TEST_CASE := ${USER}@${TARGET} ${TEST_SCRIPT}
      
      TEST_START
      [...]
      TEST = ${TEST_CASE}
      
      TEST_START
      [...]
      TEST = ${TEST_CASE}
      
      [etc]
      
      Now we just need to update the variables at the top.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      77d942ce
  11. 20 5月, 2011 4 次提交
  12. 19 5月, 2011 3 次提交
    • I
      perf stat: Add more cache-miss percentage printouts · c3305257
      Ingo Molnar 提交于
      Print out the cache-miss percentage as well if the cache refs were
      collected, for all the generic cache event types.
      
      Before:
      
         11,103,723,230 dTLB-loads                #  622.471 M/sec                    ( +-  0.30% )
             87,065,337 dTLB-load-misses          #    4.881 M/sec                    ( +-  0.90% )
      
      After:
      
         11,353,713,242 dTLB-loads                #  626.020 M/sec                    ( +-  0.35% )
            113,393,472 dTLB-load-misses          #    1.00% of all dTLB cache hits   ( +-  0.49% )
      
      Also ASCII color highlight too high percentages, them when it's executed on the console.
      
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Link: http://lkml.kernel.org/n/tip-lkhwxsevdbd9a8nymx0vxc3y@git.kernel.orgSigned-off-by: NIngo Molnar <mingo@elte.hu>
      c3305257
    • I
      perf stat: Add -d -d and -d -d -d options to show more CPU events · 2cba3ffb
      Ingo Molnar 提交于
      Print even more detailed statistics if requested via perf stat -d:
      
             -d:          detailed events, L1 and LLC data cache
          -d -d:     more detailed events, dTLB and iTLB events
       -d -d -d:     very detailed events, adding prefetch events
      
      Full output looks like this now:
      
       Performance counter stats for '/home/mingo/hackbench 10' (5 runs):
      
             1703.674707 task-clock                #    8.709 CPUs utilized            ( +-  4.19% )
                  49,068 context-switches          #    0.029 M/sec                    ( +- 16.66% )
                   8,303 CPU-migrations            #    0.005 M/sec                    ( +- 24.90% )
                  17,397 page-faults               #    0.010 M/sec                    ( +-  0.46% )
           2,345,389,239 cycles                    #    1.377 GHz                      ( +-  4.61% ) [55.90%]
           1,884,503,527 stalled-cycles-frontend   #   80.35% frontend cycles idle     ( +-  5.67% ) [50.39%]
             743,919,737 stalled-cycles-backend    #   31.72% backend  cycles idle     ( +-  8.75% ) [49.91%]
           1,314,416,379 instructions              #    0.56  insns per cycle
                                                   #    1.43  stalled cycles per insn  ( +-  2.53% ) [60.87%]
             272,592,567 branches                  #  160.003 M/sec                    ( +-  1.74% ) [56.56%]
               3,794,846 branch-misses             #    1.39% of all branches          ( +-  6.59% ) [58.50%]
             449,982,778 L1-dcache-loads           #  264.125 M/sec                    ( +-  2.47% ) [49.88%]
              22,404,961 L1-dcache-load-misses     #    4.98% of all L1-dcache hits    ( +-  6.08% ) [55.05%]
               6,204,750 LLC-loads                 #    3.642 M/sec                    ( +-  8.91% ) [43.75%]
               1,837,411 LLC-load-misses           #    1.078 M/sec                    ( +-  7.27% ) [12.07%]
             411,440,421 L1-icache-loads           #  241.502 M/sec                    ( +-  5.60% ) [36.52%]
              27,556,832 L1-icache-load-misses     #   16.175 M/sec                    ( +-  7.46% ) [46.72%]
             464,067,627 dTLB-loads                #  272.392 M/sec                    ( +-  4.46% ) [54.17%]
              10,765,648 dTLB-load-misses          #    6.319 M/sec                    ( +-  3.18% ) [48.68%]
           1,273,080,386 iTLB-loads                #  747.256 M/sec                    ( +-  3.38% ) [47.53%]
                 117,481 iTLB-load-misses          #    0.069 M/sec                    ( +- 14.99% ) [47.01%]
               4,590,653 L1-dcache-prefetches      #    2.695 M/sec                    ( +-  4.49% ) [46.19%]
               1,712,660 L1-dcache-prefetch-misses #    1.005 M/sec                    ( +-  3.75% ) [44.82%]
      
              0.195622057  seconds time elapsed  ( +-  6.84% )
      
      Also clean up the attribute construction code to be appending, and factor
      it out into add_default_attributes().
      
      Tweak the coverage percentage printout a bit, so that it's easier to view it
      alongside the +- sttddev colum.
      
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Link: http://lkml.kernel.org/n/tip-to3kgu04449s64062val8b62@git.kernel.orgSigned-off-by: NIngo Molnar <mingo@elte.hu>
      2cba3ffb
    • I
      perf bench, x86: Add alternatives-asm.h wrapper · b3132072
      Ingo Molnar 提交于
      perf bench needs this to build the kernel's memcpy routine:
      
      In file included from bench/mem-memcpy-x86-64-asm.S:2:0:
      bench/../../../arch/x86/lib/memcpy_64.S:7:33: fatal error: asm/alternative-asm.h: No such file or directory
      
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Link: http://lkml.kernel.org/n/tip-c5d41xibgullk8h2280q4gv0@git.kernel.orgSigned-off-by: NIngo Molnar <mingo@elte.hu>
      b3132072