Re: [U-Boot] [PATCH 2/3] x86: Don't copy the cpu_call64() function to a hardcoded address

2019-02-11 Thread Bin Meng
On Sat, Feb 2, 2019 at 2:06 PM Simon Glass wrote: > > On Thu, 31 Jan 2019 at 09:17, Bin Meng wrote: > > > > Before jumping to 64-bit U-Boot proper, SPL copies the cpu_call64() > > function to a hardcoded address 0x300. This can have potential > > conflicts with application usage. Switch the

Re: [U-Boot] [PATCH 2/3] x86: Don't copy the cpu_call64() function to a hardcoded address

2019-02-01 Thread Simon Glass
On Thu, 31 Jan 2019 at 09:17, Bin Meng wrote: > > Before jumping to 64-bit U-Boot proper, SPL copies the cpu_call64() > function to a hardcoded address 0x300. This can have potential > conflicts with application usage. Switch the destination address > to be allocated from the heap to avoid

[U-Boot] [PATCH 2/3] x86: Don't copy the cpu_call64() function to a hardcoded address

2019-01-31 Thread Bin Meng
Before jumping to 64-bit U-Boot proper, SPL copies the cpu_call64() function to a hardcoded address 0x300. This can have potential conflicts with application usage. Switch the destination address to be allocated from the heap to avoid such risk. Signed-off-by: Bin Meng ---