x86/crash: Indicate how well nmi_shootdown_cpus() managed to do
authorAndrew Cooper <andrew.cooper3@citrix.com>
Thu, 26 Sep 2013 08:14:51 +0000 (10:14 +0200)
committerJan Beulich <jbeulich@suse.com>
Thu, 26 Sep 2013 08:14:51 +0000 (10:14 +0200)
commitf12c1f0b09205cdf18a2c4a615fdc3e7357ce704
tree99116a0d2fb95c4a589313745fff2e08e4b0abd3
parent573fd5bd2d8bd068a6cea7ae5fcc58b962d43a78
x86/crash: Indicate how well nmi_shootdown_cpus() managed to do

Having nmi_shootdown_cpus() report which pcpus failed to be shot down is a
useful debugging hint as to what possibly went wrong (especially when the
crash logs seem to indicate that an NMI timeout occurred while waiting for one
of the problematic pcpus to perform an action).

This is achieved by swapping an atomic_t count of unreported pcpus with a
cpumask.  In the case that the 1 second timeout occurs, use the cpumask to
identify the problematic pcpus.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Keir Fraser <keir@xen.org>
xen/arch/x86/crash.c