diff options
| author | Martin Wilck <[email protected]> | 2010-06-29 15:05:31 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2010-06-29 15:29:31 -0700 |
| commit | 8d1f66dc9b4f80a1441bc1c33efa98aca99e8813 (patch) | |
| tree | 0876484c740e90568f9f0300f012e674622679c9 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 5c0c165490e763eddcbb0b6c8c41ab5cc11ddea0 (diff) | |
ipmi: set schedule_timeout_wait() value back to one
Fix a regression introduced by ae74e823cb7d ("ipmi: add parameter to limit
CPU usage in kipmid").
Some systems were seeing CPU usage go up dramatically with the recent
changes to try to reduce timer usage in the IPMI driver. This was traced
down to schedule_timeout_interruptible(1) being changed to
schedule_timeout_interruptbile(0). Revert that part of the change.
Addresses https://bugzilla.kernel.org/show_bug.cgi?id=16147
Reported-by: Thomas Jarosch <[email protected]>
Signed-off-by: Corey Minyard <[email protected]>
Tested-by: Thomas Jarosch <[email protected]>
Cc: <[email protected]> [2.6.34.x]
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions