* [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on.
@ 2014-02-25 10:57 Andrew Cooper
2014-02-25 13:03 ` Daniel Kiper
2014-03-10 11:28 ` David Vrabel
0 siblings, 2 replies; 3+ messages in thread
From: Andrew Cooper @ 2014-02-25 10:57 UTC (permalink / raw)
To: Xen-devel; +Cc: Andrew Cooper, Keir Fraser, David Vrabel, Jan Beulich
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>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
CC: David Vrabel <david.vrabel@citrix.com>
---
Changes in v2:
* Tweak wording as it moves onto a common path with kexec_reboot
---
xen/common/kexec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/common/kexec.c b/xen/common/kexec.c
index 481b0c2..23d964e 100644
--- 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 )
--
1.7.10.4
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on.
2014-02-25 10:57 [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on Andrew Cooper
@ 2014-02-25 13:03 ` Daniel Kiper
2014-03-10 11:28 ` David Vrabel
1 sibling, 0 replies; 3+ messages in thread
From: Daniel Kiper @ 2014-02-25 13:03 UTC (permalink / raw)
To: Andrew Cooper
Cc: daniel.kiper, Keir Fraser, David Vrabel, Jan Beulich, Xen-devel
On Tue, Feb 25, 2014 at 10:57:11AM +0000, Andrew Cooper wrote:
> 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>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: David Vrabel <david.vrabel@citrix.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
Daniel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on.
2014-02-25 10:57 [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on Andrew Cooper
2014-02-25 13:03 ` Daniel Kiper
@ 2014-03-10 11:28 ` David Vrabel
1 sibling, 0 replies; 3+ messages in thread
From: David Vrabel @ 2014-03-10 11:28 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Keir Fraser, Jan Beulich, Xen-devel
On 25/02/14 10:57, Andrew Cooper wrote:
> 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>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: David Vrabel <david.vrabel@citrix.com>
Acked-by: David Vrabel <david.vrabel@citrix.com>
Thanks.
David
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-03-10 11:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-25 10:57 [PATCH v2] common/kexec: Identify which cpu the kexec image is being executed on Andrew Cooper
2014-02-25 13:03 ` Daniel Kiper
2014-03-10 11:28 ` David Vrabel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.