On 30 May 2014 04:20, Dave Young dyo...@redhat.com wrote:
For ioremapped efi memory aka old_map the virt addresses are not persistant
across kexec reboot. kexec-tools will read the runtime maps from sysfs then
pass them to 2nd kernel and assuming kexec efi boot is ok. This will cause
kexec
On Fri, May 30, 2014 at 01:54:47PM +0800, Dave Young wrote:
Ccing Simon.
Simon, appologize for not ccing you about this kernel patch. I see you have
applied the userspace patch for checking sysfs runtime existance.
The userspace patch depends on this patch but it is not harmful even
On Fri, May 30, 2014 at 11:20:10AM +0800, Dave Young wrote:
For ioremapped efi memory aka old_map the virt addresses are not persistant
across kexec reboot. kexec-tools will read the runtime maps from sysfs then
pass them to 2nd kernel and assuming kexec efi boot is ok. This will cause
kexec
On Fri, May 30, 2014 at 11:20:10AM +0800, Dave Young wrote:
For ioremapped efi memory aka old_map the virt addresses are not persistant
across kexec reboot. kexec-tools will read the runtime maps from sysfs then
pass them to 2nd kernel and assuming kexec efi boot is ok. This will cause
kexec
For ioremapped efi memory aka old_map the virt addresses are not persistant
across kexec reboot. kexec-tools will read the runtime maps from sysfs then
pass them to 2nd kernel and assuming kexec efi boot is ok. This will cause
kexec boot failure.
To address this issue do not export runtime maps
Ccing Simon.
Simon, appologize for not ccing you about this kernel patch. I see you have
applied the userspace patch for checking sysfs runtime existance.
The userspace patch depends on this patch but it is not harmful even without
this kernel patch. So applying the userspace patch before this
