From: Simon Horman <horms@verge.net.au>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: kexec@lists.infradead.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: kdump: A memory hotplug issue on s390
Date: Thu, 27 Oct 2011 07:31:26 +0900 [thread overview]
Message-ID: <20111026223126.GA9754@verge.net.au> (raw)
In-Reply-To: <1319563037.3056.30.camel@br98xy6r>
On Tue, Oct 25, 2011 at 07:17:17PM +0200, Michael Holzheu wrote:
> Hello Simon and Vivek,
>
> For s390 we currently use /proc/iomem for defining the memory layout in
> the kexec elfcore header. Unfortunately this is not correct, when using
> memory hotplug. When a memory chunk is set offline (e.g. with "echo
> offline > /sys/devices/system/memory/memoryX/state") this is not
> reflected in /proc/iomem.
>
> To fix this I could parse /sys/devices/system/memory and exclude each
> memory chunk that in not online from the /proc/iomem info. Do you think
> that this approach is fine or is there a better solution?
Hi Michael,
that sounds like a reasonable approach to me.
IIRC, kexec xen on ia64 makes use of an alternate iomem file,
and this seems to be another example of /proc/iomem not being
the right source of information.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-10-26 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 17:17 kdump: A memory hotplug issue on s390 Michael Holzheu
2011-10-26 22:31 ` Simon Horman [this message]
2011-10-27 17:28 ` Vivek Goyal
2011-10-27 18:15 ` Michael Holzheu
2011-10-27 18:33 ` Vivek Goyal
2011-10-28 13:35 ` [PATCH] kexec-tools: s390: Fix memory detection for memory hotplug Michael Holzheu
2011-10-31 6:40 ` 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=20111026223126.GA9754@verge.net.au \
--to=horms@verge.net.au \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
/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.