Hi, On Fri, 2016-07-29 at 16:58 -0600, Goel, Sameer wrote: > 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 Your patch no longer applies. Please rebase it to my for-merge-arm64-v2 branch and re-post. -Geoff
