Hello Vivek, On Mon, 2011-08-01 at 16:16 -0400, Vivek Goyal wrote: > On Wed, Jul 27, 2011 at 02:55:05PM +0200, Michael Holzheu wrote: > > From: Michael Holzheu <holzheu@xxxxxxxxxxxxxxxxxx> > > > > On s390 there is a different KEXEC_CONTROL_MEMORY_LIMIT for the normal and > > the kdump kexec case. Therefore this patch introduces a new macro > > KEXEC_CRASH_CONTROL_MEMORY_LIMIT. This is set to > > KEXEC_CONTROL_MEMORY_LIMIT for all architectures that do not define > > KEXEC_CRASH_CONTROL_MEMORY_LIMIT. > > Hi Michael, > > Curious that why limit is different for kexec and kdump cases on s390 > only. The standard kexec relocate_kernel code calls a machine instruction that must run below 2 GiB. For kdump we currently do not use the control page at all because no segments have to be moved in that case. Perhaps I am still missing something here? Michael -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
