1. 19 1月, 2014 1 次提交
    • S
      ktest: Add BISECT_TRIES to bisect test · 961d9cac
      Steven Rostedt (Red Hat) 提交于
      For those cases that it takes several tries to hit a bug, it would be
      useful for ktest.pl to try a test multiple times before it considers
      the test as a pass. To accomplish this, BISECT_TRIES ktest config
      option has been added. It is default to one, as most of the time a
      bisect only needs to try a test once. But the user can now up this
      to make ktest run a given test multiple times. The first failure
      that is detected will set a bisect bad. It only repeats on success.
      
      Note, as with all race bugs, there's no guarantee that if it succeeds,
      it is really a good bisect. But it helps in case the bug is somewhat
      reliable.
      
      You can set BISECT_TRIES to zero, and all tests will be considered
      good, unless you also set BISECT_MANUAL.
      Suggested-by: N"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      961d9cac
  2. 18 12月, 2013 1 次提交
  3. 12 12月, 2013 2 次提交
    • S
      ktest: Add eval '=~' command to modify variables in config file · c75d22d9
      Steven Rostedt (Red Hat) 提交于
      With the added variable ${KERNEL_VERSION}, it is useful to be
      able to use parts of it for other variables.
      
      For example, if you want to create a warnings file for each major
      kernel version to test sub versions against you can create
      your warnings file with like this:
      
        WARNINGS_FILE = warnings-file-${KERNEL_VERSION}
      
      But this may add 3.8.12 or something, and we want all 3.8.* to
      use the same file, and 3.10.* to use another file, and so on.
      With the eval command we can, by adding:
      
        WARNINGS_FILE =~ s/(-file-\d+\.\d+).*/$1/
      
      Which will chop off the extra characters after the 3.8.
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      c75d22d9
    • S
      ktest: Add special variable ${KERNEL_VERSION} · 8e80bf05
      Steven Rostedt (Red Hat) 提交于
      Add a special variable that can be used in other variables called
      ${KERNEL_VERSION}. This will embed the current kernel version into
      the variable. For example:
      
      WARNINGS_FILE = ${OUTPUT_DIR}/warnings-${KERNEL_VERSION}
      
      If the current version is v3.8 then the WARNINGS_FILE will become
      
        ${OUTPUT_DIR}/warnings-v3.8
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      8e80bf05
  4. 05 12月, 2013 1 次提交
    • H
      usb: tools: fix a regression issue that gcc can't link to pthread · cb292ce2
      Huang Rui 提交于
      Reproduce:
      ray@hr-bak:~/usb$ make -C tools/usb/
      make: Entering directory `/home/ray/usb/tools/usb'
      gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c
      /tmp/cc0EMxfy.o: In function `main':
      /home/ray/usb/tools/usb/testusb.c:508: undefined reference to `pthread_create'
      /home/ray/usb/tools/usb/testusb.c:531: undefined reference to `pthread_join'
      collect2: error: ld returned 1 exit status
      make: *** [testusb] Error 1
      make: Leaving directory `/home/ray/usb/tools/usb'
      
      Comments:
      In the latest version (4.7.3) of gcc compiler, it requres that
      libraries must follow the object or source files like below:
      
      "gcc hello.c -lpthread" instead of "gcc -lpthread hello.c"
      
      And it isn't encountered at gcc version 4.7.2.
      So this patch fix to move the pthread option after testusb.c.
      Signed-off-by: NHuang Rui <ray.huang@amd.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      cb292ce2
  5. 04 12月, 2013 31 次提交
  6. 27 11月, 2013 4 次提交