37 lines
1.2 KiB
Diff
37 lines
1.2 KiB
Diff
|
# Commit 4509ada6ba1f09cc8f4fa23e009e7e5a963b6086
|
||
|
|
# Date 2014-03-10 11:11:28 +0100
|
||
|
|
# Author Andrew Cooper <andrew.cooper3@citrix.com>
|
||
|
|
# Committer Jan Beulich <jbeulich@suse.com>
|
||
|
|
kexec: identify which cpu the kexec image is being executed on
|
||
|
|
|
||
|
|
A patch to this effect has been in XenServer for a little while, and has
|
||
|
|
proved to be a useful debugging point for servers which have different
|
||
|
|
behaviours depending when crashing on the non-bootstrap processor.
|
||
|
|
|
||
|
|
Moving the printk() from kexec_panic() to one_cpu_only() means that it will
|
||
|
|
only be printed for the cpu which wins the race along the kexec path.
|
||
|
|
|
||
|
|
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
|
||
|
|
Acked-by: David Vrabel <david.vrabel@citrix.com>
|
||
|
|
|
||
|
|
--- a/xen/common/kexec.c
|
||
|
|
+++ b/xen/common/kexec.c
|
||
|
|
@@ -265,6 +265,8 @@ static int noinline one_cpu_only(void)
|
||
|
|
}
|
||
|
|
|
||
|
|
set_bit(KEXEC_FLAG_IN_PROGRESS, &kexec_flags);
|
||
|
|
+ printk("Executing kexec image on cpu%u\n", cpu);
|
||
|
|
+
|
||
|
|
return 0;
|
||
|
|
}
|
||
|
|
|
||
|
|
@@ -340,8 +342,6 @@ void kexec_crash(void)
|
||
|
|
if ( !test_bit(KEXEC_IMAGE_CRASH_BASE + pos, &kexec_flags) )
|
||
|
|
return;
|
||
|
|
|
||
|
|
- printk("Executing crash image\n");
|
||
|
|
-
|
||
|
|
kexecing = TRUE;
|
||
|
|
|
||
|
|
if ( kexec_common_shutdown() != 0 )
|