[PATCH] [RFC] sh: kexec: Register crashk_res
lethal at linux-sh.org
Mon Sep 5 00:36:27 EDT 2011
On Mon, Sep 05, 2011 at 01:25:50PM +0900, Simon Horman wrote:
> On Mon, Sep 05, 2011 at 12:23:53PM +0900, Paul Mundt wrote:
> > On Fri, Sep 02, 2011 at 12:47:12PM +0900, Simon Horman wrote:
> > > Register crashk_res so that it can be used by kexec-tools
> > > via /proc/iomem.
> > >
> > > On x86 the registration occurs using
> > > insert_resource(&iomem_resource, &crashk_res).
> > > However that approach seems to result in the boot hanging on SH.
> > >
> > > Signed-off-by: Simon Horman <horms at verge.net.au>
> > x86 has a slightly more straightforward registration method. We end up
> > going through the same path for all memory ranges, which also
> > encapsulates the NUMA case. As such, we don't necessarily know which
> > range will contain the resource in question, so it's attempted on each
> > range addition, expecting the resource manager to work things out for us.
> > With the request_resource() in place you presumably see the crash kernel
> > resource where you expect it to in /proc/iomem?
> Yes. With this patch in place the crash kernel resource
> shows up in /proc/iomem in a sensible way.
> # cat /proc/iomem
> 40000000-4effffff : System RAM
> 40001000-402dbfc7 : Kernel code
> 402dbfc8-403cd51f : Kernel data
> 40553000-40568c5b : Kernel bss
> 4d000000-4effffff : Crash kernel
Ok, I've queued it up with a slightly more verbose changelog. I'll send
it along for 3.1 so kexec-tools doesn't remain blocked.
More information about the kexec