summaryrefslogtreecommitdiff
path: root/proto_mpls_unicast.c
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2015-10-24 17:38:08 +0300
committerTobias Klauser <tklauser@distanz.ch>2015-10-26 13:29:20 +0100
commitecfd9fb37218c6a2433074432b6dfa1ef2ca392e (patch)
tree298b05d8ca4bffa101f0aeb8f8f1e306f81f7eff /proto_mpls_unicast.c
parente97a3b2a56efdb1833c6f1228f50b2636977647e (diff)
flowtop: man: Add notice about rate info
Add notice about rate info to the feature list. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'proto_mpls_unicast.c')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-23 03:44:07 +0000
k 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 'tools/perf/scripts/python/sctop.py')