28 Jun, 2006

3 commits


29 Mar, 2006

1 commit


26 Mar, 2006

1 commit

  • MODULE_PARM was actually breaking: recent gcc version optimize them out as
    unused. It's time to replace the last users, which are generally in the
    most unloved drivers anyway.

    Signed-off-by: Rusty Russell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rusty Russell
     

24 Mar, 2006

1 commit

  • A long-running rcutorture test can overflow dmesg, so that the line
    containing the module parameters is lost. Although it is usually possible
    to retrieve this information from the log files, it is much better to just
    tag it onto the final success/failure line so that it may be easily found.
    This patch does just that.

    Signed-off-by: "Paul E. McKenney"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Paul E. McKenney
     

01 Feb, 2006

1 commit

  • rcu_torture_lock is used in a softirq-unsafe manner, but it is also
    taken by rcu_torture_cb(), which may execute in softirq-context,
    resulting in potential deadlocks.

    The fix is to acquire rcu_torture_lock in a softirq-safe manner. With
    this fix applied, the rcu-torture code passes validation.

    Signed-off-by: Ingo Molnar
    Acked-by: Paul E. McKenney
    Signed-off-by: Linus Torvalds

    Ingo Molnar
     

09 Jan, 2006

3 commits


13 Dec, 2005

1 commit

  • While doing some test of RCU torture module, I hit a OOPS in rcu_do_batch,
    which was trying to processes callback of a module that was just removed.
    This is because we weren't waiting long enough for all callbacks to fire.

    Signed-off-by: Srivatsa Vaddagiri
    Cc: Dipankar Sarma
    Acked-by: "Paul E. McKenney"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Srivatsa Vaddagiri
     

18 Nov, 2005

1 commit

  • One issue with the RCU torture test is that the current error flagging can
    be lost in dmesg. This patch adds a "SUCCESS"/"FAILURE" string to the line
    that flags the end of the test, where it can easily be seen with "dmesg |
    tail" at the end of the test. Also adds tests of architecture-specific
    memory barriers -- or, more likely, of the RCU torture test itself.

    Cc:
    Signed-off-by: "Paul E. McKenney"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Paul E. McKenney
     

14 Nov, 2005

1 commit

  • Make the box usable for interactive work when running the RCU torture test,
    by renicing the RCU torture-test threads to +19 by default. Kthreads run
    at nice -5 by default.

    Signed-off-by: Ingo Molnar
    Acked-by: Paul E. McKenney"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ingo Molnar
     

31 Oct, 2005

1 commit

  • This patch is a rewrite of the one submitted on October 1st, using modules
    (http://marc.theaimsgroup.com/?l=linux-kernel&m=112819093522998&w=2).

    This rewrite adds a tristate CONFIG_RCU_TORTURE_TEST, which enables an
    intense torture test of the RCU infratructure. This is needed due to the
    continued changes to the RCU infrastructure to accommodate dynamic ticks,
    CPU hotplug, realtime, and so on. Most of the code is in a separate file
    that is compiled only if the CONFIG variable is set. Documentation on how
    to run the test and interpret the output is also included.

    This code has been tested on i386 and ppc64, and an earlier version of the
    code has received extensive testing on a number of architectures as part of
    the PREEMPT_RT patchset.

    Signed-off-by: "Paul E. McKenney"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Paul E. McKenney