From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [Patch] common/kexec: Identify which cpu the kexec image is being executed on. Date: Mon, 6 Jan 2014 17:39:28 +0000 Message-ID: <52CAEA50.8010702@citrix.com> References: <1389009547-12886-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1389009547-12886-1-git-send-email-andrew.cooper3@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: Keir Fraser , David Vrabel , Jan Beulich , Xen-devel List-Id: xen-devel@lists.xenproject.org On 06/01/14 11:59, 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 > not be printed multiple times in the case of multiple cpus racing on the kexec > path. > > Signed-off-by: Andrew Cooper > CC: Keir Fraser > CC: Jan Beulich > CC: David Vrabel Acked-by: David Vrabel One for 4.5 I think. David