On Wed, Jan 15, 2014 at 09:26:14AM -0800, H. Peter Anvin wrote: > On 01/15/2014 09:05 AM, Vivek Goyal wrote: > > > > I think this is a reasonable approach to solve the issue. Use a command > > line to not bring up specific cpu in second kernel which can create > > problems. > > > > Acked-by: Vivek Goyal <vgoyal at redhat.com> > > > > hpa, I know you are not excited about this approach. If you made up your > > mind that this appoarch is not worth pursuing, please do suggest what > > would you like to see and we can give that a try. > > > > We want to solve this problem as on large memory machines saving dump can > > take lot of time and we want to bring up multiple cpus and speed up > > compression and save on dump time. > > > > I'm not excited about kdump's reliance on the command line, since it > seems to be a neverending source of trouble, simply because the command > line is fundamentally intended as a human interface. So in general, what are the alternatives? Either we figure out that kernel is booting as kdump kernel and do things differently. That seems even worse as what do we want in kdump kernel will change over a period of time. Other thing is that pass more information in bootparams. But that does not seem much different than command line to me. > However, this > seems relatively harmless in comparison with everything else and I am > much happier with saving the ID in the first kernel rather than trying > to guess if a currently-downed CPU is the BSP. So looks like you are alright with this patch. Can you please queue it up in your tree. Thanks Vivek
