Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Ard, On Wed, Mar 07, 2018 at 07:55:34PM +, Ard Biesheuvel wrote: > (+ James) > > Hello Akashi, > > On 6 March 2018 at 09:00, AKASHI Takahiro wrote: > > Tyler, Jeffrey, > > > > On Fri, Mar 02, 2018 at 08:27:11AM -0500, Tyler Baicar wrote: > >> On 3/2/2018 12:53

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

(+ James) Hello Akashi, On 6 March 2018 at 09:00, AKASHI Takahiro wrote: > Tyler, Jeffrey, > > On Fri, Mar 02, 2018 at 08:27:11AM -0500, Tyler Baicar wrote: >> On 3/2/2018 12:53 AM, AKASHI Takahiro wrote: >> >Tyler, Jeffrey, >> > >> >[Note: This issue takes place in

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Hello Akashi, On 3/6/2018 4:00 AM, AKASHI Takahiro wrote: Tyler, Jeffrey, On Fri, Mar 02, 2018 at 08:27:11AM -0500, Tyler Baicar wrote: On 3/2/2018 12:53 AM, AKASHI Takahiro wrote: Tyler, Jeffrey, [Note: This issue takes place in kexec, not kdump. So to be precise, it is not the same

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Tyler, Jeffrey, On Fri, Mar 02, 2018 at 08:27:11AM -0500, Tyler Baicar wrote: > On 3/2/2018 12:53 AM, AKASHI Takahiro wrote: > >Tyler, Jeffrey, > > > >[Note: This issue takes place in kexec, not kdump. So to be precise, > >it is not the same phenomenon as what I addressed in [1],[2]: > > [1] >

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

On 3/2/2018 12:53 AM, AKASHI Takahiro wrote: Tyler, Jeffrey, [Note: This issue takes place in kexec, not kdump. So to be precise, it is not the same phenomenon as what I addressed in [1],[2]: [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-February/557254.html [2]

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Hi, On Wed, Feb 28, 2018 at 08:39:42AM -0700, Jeffrey Hugo wrote: > On 2/27/2018 11:19 PM, AKASHI Takahiro wrote: > >Tyler, > > > ># I missed catching your patch as its subject doesn't contain arm64. > > > >On Fri, Feb 23, 2018 at 12:42:31PM -0700, Tyler Baicar wrote: > >>Currently on arm64 ESRT

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

On 2/27/2018 11:19 PM, AKASHI Takahiro wrote: Tyler, # I missed catching your patch as its subject doesn't contain arm64. On Fri, Feb 23, 2018 at 12:42:31PM -0700, Tyler Baicar wrote: Currently on arm64 ESRT memory does not appear to be properly blocked off. Upon successful initialization,

Re: [PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Tyler, # I missed catching your patch as its subject doesn't contain arm64. On Fri, Feb 23, 2018 at 12:42:31PM -0700, Tyler Baicar wrote: > Currently on arm64 ESRT memory does not appear to be properly blocked off. > Upon successful initialization, ESRT prints out the memory region that it >

[PATCH 0/2] ESRT fixes for relocatable kexec'd kernel

Currently on arm64 ESRT memory does not appear to be properly blocked off. Upon successful initialization, ESRT prints out the memory region that it exists in like: esrt: Reserving ESRT space from 0x0a4c1c18 to 0x0a4c1cf0. But then by dumping /proc/iomem this region appears as