summaryrefslogtreecommitdiff
path: root/kexec/kexec.c
diff options
context:
space:
mode:
authorChandru <chandru@in.ibm.com>2010-03-02 16:09:49 +0530
committerSimon Horman <horms@verge.net.au>2010-03-03 08:32:09 +1100
commit5996651eccbffb7c195c2911f37fda2f2258e48d (patch)
treed9638fb5c82ab3d3739ce9acd290f694b5049267 /kexec/kexec.c
parent0e669a27ec55d2baaf47fdab87da08ed189b5ac6 (diff)
kexec/kdump: RMO region does not exist in drconf memory
The RMO region can only exist in '/memory@0' node in the device tree. While adding support for '/ibm,dynamic-reconfiguration-memory' in kexec-tools, I incorrectly extended the code of '/memory@' nodes to drconf memory with the assumption that what applies to '/memory@' nodes would also apply to drconf memory. This is incorrect and hence removing the code from kexec-tools now. With this code in place, kexec on kexec fails. The first kexec works because '/memory@0' node is read after drconf memory and that correctly sets rmo_base and rmo_top from '/memory@0' node. While in the kexec'ed kernel, '/ibm,dynamic-reconfiguration-memory' is read after '/memory@xxx' nodes and this incorrectly sets both rmo_base and rmo_top from drconf memory. Sorry for introducing this bug. Signed-off-by: Chandru Siddalingappa <chandru@linux.vnet.ibm.com> Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'kexec/kexec.c')
0 files changed, 0 insertions, 0 deletions