diff options
| author | John Stultz <[email protected]> | 2014-03-27 23:30:49 +0000 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2014-03-28 07:07:07 +0000 |
| commit | cab5e127eef040399902caa8e1510795583fa03a (patch) | |
| tree | 9e9a5713d4d58ffafea24354537e8207bd013c7e /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | vfs: Allocate anon_inode_inode in anon_inode_init() (diff) | |
| download | kernel-cab5e127eef040399902caa8e1510795583fa03a.tar.gz kernel-cab5e127eef040399902caa8e1510795583fa03a.zip | |
time: Revert to calling clock_was_set_delayed() while in irq context
In commit 47a1b796306356f35 ("tick/timekeeping: Call
update_wall_time outside the jiffies lock"), we moved to calling
clock_was_set() due to the fact that we were no longer holding
the timekeeping or jiffies lock.
However, there is still the problem that clock_was_set()
triggers an IPI, which cannot be done from the timer's hard irq
context, and will generate WARN_ON warnings.
Apparently in my earlier testing, I'm guessing I didn't bump the
dmesg log level, so I somehow missed the WARN_ONs.
Thus we need to revert back to calling clock_was_set_delayed().
Signed-off-by: John Stultz <[email protected]>
Cc: Linus Torvalds <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions