[PATCH] kexec/kdump: RMO region does not exist in drconf memory

Simon Horman horms at verge.net.au
Tue Mar 2 16:33:21 EST 2010


On Tue, Mar 02, 2010 at 04:09:49PM +0530, Chandru wrote:
> The RMO region can only exist in '/memory at 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 at 0' node is read after drconf memory and
> that correctly sets rmo_base and rmo_top from '/memory at 0' node.
> While in the kexec'ed kernel, '/ibm,dynamic-reconfiguration-memory'
> is read after '/memory at xxx' nodes and this incorrectly sets both
> rmo_base and rmo_top from drconf memory.

Thanks, applied.




More information about the kexec mailing list