Hi Geoff,
In our setup we cannot place the kernel starting at 0 address. So, it it
placed at the first valid aligned address after placing the reserved
regions in memory.
The code from the change (https://patchwork.kernel.org/patch/8325221/)
adds the reserved regions to iomem ranges. So, when the kexec tool is
run it picks up the first reserved region as the start address for
physical ram. When the kernel is loaded at this address, it fails to boot.
So, I have put in a filter in the code that would pick up the right
address of the primary kernel after this change was introduced.
Thanks,
Sameer
On 6/10/2016 10:41 AM, Geoff Levand wrote:
Hi Sameer,
On Tue, 2016-04-26 at 16:14 -0600, Sameer Goel wrote:
Starting 4.6-rc4 the kernel memblock start is rounded down to a desirable
alignment. So, the kernel can see reserved memory regions before the kernel
start address in the iomem query.
Need to make sure that the right kernel start address is picked from the iomem
query.
---
It is still in question whether or not your's is the correct
fix. Could you provide a test case that hits this problem
so we can work on the solution?
Thanks.
-Geoff
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
