Re: [PATCH 3/3] arm64: memory: Give hotplug memory a different resource name

2020-04-22 Thread James Morse
Hi Eric, On 15/04/2020 21:37, Eric W. Biederman wrote: > James Morse writes: > >> If kexec chooses to place the kernel in a memory region that was >> added after boot, we fail to boot as the kernel is running from a >> location that is not described as memory by the UEFI memory map or >> the

Re: [PATCH 3/3] arm64: memory: Give hotplug memory a different resource name

2020-04-15 Thread Eric W. Biederman
James Morse writes: > If kexec chooses to place the kernel in a memory region that was > added after boot, we fail to boot as the kernel is running from a > location that is not described as memory by the UEFI memory map or > the original DT. > > To prevent unaware user-space kexec from doing

Re: [PATCH 3/3] arm64: memory: Give hotplug memory a different resource name

2020-03-30 Thread David Hildenbrand
On 26.03.20 19:07, James Morse wrote: > If kexec chooses to place the kernel in a memory region that was > added after boot, we fail to boot as the kernel is running from a > location that is not described as memory by the UEFI memory map or > the original DT. > > To prevent unaware user-space

[PATCH 3/3] arm64: memory: Give hotplug memory a different resource name

2020-03-26 Thread James Morse
If kexec chooses to place the kernel in a memory region that was added after boot, we fail to boot as the kernel is running from a location that is not described as memory by the UEFI memory map or the original DT. To prevent unaware user-space kexec from doing this accidentally, give these