From: Simon Horman <horms@verge.net.au>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] Don't use /sys/firmware/memmap for Xen
Date: Fri, 28 Nov 2008 13:53:42 +0900 [thread overview]
Message-ID: <20081128045340.GE23112@verge.net.au> (raw)
In-Reply-To: <1227690039-16014-1-git-send-email-bwalle@suse.de>
On Wed, Nov 26, 2008 at 10:00:39AM +0100, Bernhard Walle wrote:
> On Xen, we have to use /proc/iomem to retrieve the memory area for the kexec'd
> kernel, not /sys/firmware/memmap. Dom0 kernel gets a E820 map that contains
> only one region:
>
> 0000000000000000-0000000018e5e000 (System RAM)
>
> Compared to the /proc/iomem:
>
> 00000000-0009cbff : System RAM
> 0009cc00-0009ffff : reserved
> 000ce000-000d3fff : reserved
> 000e0000-000fffff : reserved
> 00100000-1fd6ffff : System RAM
> 01000000-04ffffff : Crash kernel
> 1ec00000-1fbfffff : Hypervisor code and data
> 1f0b4680-1f0b4873 : Crash note
> 1f0b4900-1f0b4a93 : Crash note
> 1f0b4b80-1f0b4d13 : Crash note
> 1f0b4e00-1f0b4f93 : Crash note
> ...
>
> Without that patch, /proc/vmcore is empty in the kexec'd kernel and I'm unable
> to copy the crashdump.
Thanks Bernhard, applied.
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-11-28 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 9:00 [PATCH] Don't use /sys/firmware/memmap for Xen Bernhard Walle
2008-11-28 4:53 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 12:49 Bernhard Walle
2008-11-26 8:46 ` Bernhard Walle
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=20081128045340.GE23112@verge.net.au \
--to=horms@verge.net.au \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.