From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] [RFC] sh: kexec: Register crashk_res
Date: Mon, 05 Sep 2011 04:36:27 +0000 [thread overview]
Message-ID: <20110905043627.GD22142@linux-sh.org> (raw)
In-Reply-To: <1314935232-1545-1-git-send-email-horms@verge.net.au>
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@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.
next prev parent reply other threads:[~2011-09-05 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 3:47 [PATCH] [RFC] sh: kexec: Register crashk_res Simon Horman
2011-09-05 3:23 ` Paul Mundt
2011-09-05 4:25 ` Simon Horman
2011-09-05 4:36 ` Paul Mundt [this message]
2011-09-05 5:30 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110905043627.GD22142@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox