From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: kexec: Check segment memory addresses
Date: Fri, 7 Sep 2012 09:49:38 +0100 [thread overview]
Message-ID: <20120907084937.GC13739@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1347007260-13271-3-git-send-email-matthew.leach@arm.com>
On Fri, Sep 07, 2012 at 09:41:00AM +0100, Matthew Leach wrote:
> Ensure that the memory regions that are set within the segments
> correspond to physical contiguous memory regions.
>
> Reviewed-by: Simon Horman <horms@verge.net.au>
> Reviewed-by: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Matthew Leach <matthew.leach@arm.com>
What about platforms which pull out bits of physical RAM from memblock
via arm_memblock_steal() ? Doesn't this mean such platforms will reduce
their available memory on each subsequent kexec?
next prev parent reply other threads:[~2012-09-07 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 8:40 [PATCH 0/2] ARM: kexec: Add dtb kexce support Matthew Leach
2012-09-07 8:40 ` [PATCH 1/2] ARM: kexec: scan for dtb magic in segments Matthew Leach
2012-09-07 8:41 ` [PATCH 2/2] ARM: kexec: Check segment memory addresses Matthew Leach
2012-09-07 8:49 ` Russell King - ARM Linux [this message]
2012-09-07 10:04 ` Will Deacon
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=20120907084937.GC13739@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).