On 20/06/16 12:08, Jan Beulich wrote: > Quite frequently the watchdog would hit an innocent CPU, e.g. one > trying to acquire a spin lock a remote CPU holds for extended periods > of time, or a random CPU in TSC calbration rendezvous. In such cases > the register and stack dump for that CPU doesn't really help in the > analysis of the problem. > > To keep things reasonable on large systems, only log CS:RIP by default. > This can be overridden via a new command line option such that full > register/stack state would get logged. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> > Reviewed-by: Andrew Cooper <andrew.coop...@citrix.com> > --- > v3: Add timeout. (Andrew, I hope the R-b can be kept despite the logic > not being a 1:1 clone of what the crash dump path does.)
Yeah - looks good. ~Andrew
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
