t treat EfiBootServices{Code,Data} as normal RAM under /mapbs
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/arm/efi/efi-boot.h
> +++ b/xen/arch/arm/efi/efi-boot.h
> @@ -131,9 +131,10 @@ static EFI_STATUS __init efi_process_mem
>
> for ( Index = 0; Index < (mmap_size
On Wed, Jun 10, 2015 at 11:12 AM, Andrew Cooper
wrote:
> On 10/06/15 18:22, Roy Franz wrote:
>>
>>>> I read it backwards and thought this was currently excluding them like
>>>> x86 does.
>>>>
>>>> Am I correct that the stricter x86
On Wed, Jun 10, 2015 at 2:37 AM, Jan Beulich wrote:
On 10.06.15 at 11:26, wrote:
>> On Wed, 2015-06-10 at 10:15 +0100, Jan Beulich wrote:
>>> >>> On 10.06.15 at 10:56, wrote:
>>> > On Tue, 2015-06-09 at 14:53 +0100, Jan Beulich wrote:
>>> >> From: Konrad Rzeszutek Wilk
>>> >>
>>> >> To hel
hange looks ok to me, what do you think?
Yeah, this should be fine. Most EFI allocations have page-size
granularity within the firmware,
so there wasn't much point doing something smaller. I haven't
actually used firmware that
changed the memmap size on ExitBootServices, so that size wa
On Mon, Mar 2, 2015 at 10:43 AM, Roy Franz wrote:
> On Mon, Mar 2, 2015 at 9:21 AM, Stefano Stabellini
> wrote:
>> On Fri, 30 Jan 2015, Daniel Kiper wrote:
>>> We need more fine grained knowledge about EFI environment and check
>>> for EFI platform and EFI loader
On Mon, Mar 2, 2015 at 9:23 AM, Jan Beulich wrote:
On 30.01.15 at 18:54, wrote:
>> --- a/xen/arch/x86/efi/efi-boot.h
>> +++ b/xen/arch/x86/efi/efi-boot.h
>> @@ -103,9 +103,35 @@ static void __init relocate_trampoline(unsigned long
>> phys)
>> *(u16 *)(*trampoline_ptr + (long)trampo
On Mon, Mar 2, 2015 at 9:21 AM, Stefano Stabellini
wrote:
> On Fri, 30 Jan 2015, Daniel Kiper wrote:
>> We need more fine grained knowledge about EFI environment and check
>> for EFI platform and EFI loader separately to properly support
>> multiboot2 protocol. In general Xen loaded by this protoc
On Thu, Dec 4, 2014 at 1:35 AM, Jan Beulich wrote:
On 03.12.14 at 22:02, wrote:
>> Hey,
>>
>> 1) Why is there in EFI code so many functions (e.g. efi_start(),
>>efi_arch_edd(), ...) with local variables declared as a static?
>>Though some of them have also regular local variables. I
should be found as it got added in the 1st pass,
> - the various "linux,uefi-*" nodes all got added during the 1st pass
> and hence only their contents may get updated.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Roy Franz
I built and tested this, however since my firm