On 28 May 2014 15:51, Vivek Goyal <vgo...@redhat.com> wrote: > On Wed, May 28, 2014 at 10:09:35AM +0800, Dave Young wrote: > > [..] >> > I've only vaguely been following along with the other thread, so please >> > summarise everything again in your patch. Particularly, I need answers >> > to the following questions, >> > >> > - Are you trying to fix a kexec/kdump regression? >> >> Somehow it is a regression. > > Well, it is a *regression*. Previously kdump would work with > SGI UV machines as it used "noefi". Now kexec by default thinks that > efi is enabled and 1:1 mappings are in place and that does not work > with SGI UV machines.
So, if someone boots an SGI UV machine with the "noefi" kernel command line parameter, the kernel still creates /sys/firmware/efi/runtime-map/ ? Why does kexec/kdump think a kernel booted with "noefi" supports EFI? Or are we talking about a different "noefi" parameter? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
