Re: [PATCH v3 02/31] arm64: Kernel booting and initialisation
From: Nicolas Pitre
Date: Mon Sep 10 2012 - 11:00:06 EST
On Mon, 10 Sep 2012, Arnd Bergmann wrote:
> On Monday 10 September 2012, Nicolas Pitre wrote:
> > On Mon, 10 Sep 2012, Arnd Bergmann wrote:
> > > On Monday 10 September 2012, Catalin Marinas wrote:
> > > > On Mon, Sep 10, 2012 at 06:53:39AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > I think a bunch of other architectures can have relocatable kernels, which
> > > is useful e.g. for kdump. It does imply a small runtime cost and may have
> > > other disadvantages though.
> > Relocatable in physical space is what kdump actually needs, and that's
> > what we already have here (as well as on ARM32 for that matter with
> > CONFIG_ARM_PATCH_PHYS_VIRT). Relocatable in the virtual space is costly
> > and we shouldn't need to go there.
> Ah, I see. I thought that the other architectures (powerpc and x86)
> doing this were actually building with -fPIC, but they do the same
> kind of early patching that we do.
This being said, on ARM we don't take advantage of this physically
relocatable attribute with kdump. Granted, PATCH_PHYS_VIRT was
introduced after kdump support, therefore the kernel had to be copied at
its expected physical location after the memory content there had been
preserved. These days the only thing that kdump would need to do is to
just boot the kdump kernel in place with its reserved memory range and
let it ioremap the previous kernel's memory for analysis.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/