Re: [Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

>>> On 16.01.18 at 18:43, wrote: > On 12/01/18 13:13, Jan Beulich wrote: > On 09.01.18 at 20:43, wrote: >>> When I compiled the snippet on x86 and Arm, no relocation is available >>> for the pointers to string in the array in the final

Re: [Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

Hi Jan, On 12/01/18 13:13, Jan Beulich wrote: On 09.01.18 at 20:43, wrote: When I compiled the snippet on x86 and Arm, no relocation is available for the pointers to string in the array in the final binary. Yet they are available in the object. I can see them there

Re: [Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

>>> On 09.01.18 at 20:43, wrote: > When I compiled the snippet on x86 and Arm, no relocation is available > for the pointers to string in the array in the final binary. Yet they > are available in the object. I can see them there in the binary I look at. I use my own

Re: [Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

Hi Jan, On 01/02/2018 04:35 PM, Jan Beulich wrote: On 21.12.17 at 15:55, wrote: The EFI image should be relocatable. At the moment, all the stub is relocatable but one place. Do you really mean relocatable here? Based on ... Hmm yes position independent. On

[Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

The EFI image should be relocatable. At the moment, all the stub is relocatable but one place. On both Arm64 and x86-64 (from a quick glance) , the compiler will generate absolute pointer in the ErrCodeToStr array. Those values are based on Xen view of the virtual memory and may not be the same