summaryrefslogtreecommitdiff
path: root/bpfc.zsh
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2014-06-16 11:08:32 +0200
committerTobias Klauser <tklauser@distanz.ch>2014-06-16 11:08:32 +0200
commit6424dd90f721fd968c1159236f525ed59f355045 (patch)
tree8d68a62ea5d622f3e974f392c1bcd36c1e2e4293 /bpfc.zsh
parentb25471fa58187da3116c2dc5bb10e8c007d66039 (diff)
netsniff-ng 0.5.9-rc2v0.5.9-rc2
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'bpfc.zsh')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-18 18:07:02 +0000
table>
x86/mce: Make timer handling more robust
Erik reported that on a preproduction hardware a CMCI storm triggers the BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is started by the CMCI logic before the MCE CPU hotplug callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'Documentation/mmc/mmc-tools.txt')