Re: [Xen-devel] ARM: ACPI boot failure

[Julien Grall <julien.grall@xxxxxxx>]

On 08/02/17 09:27, Vijay Kilari wrote:
> Hi Daniel,
Hello,

>    After git bisect, I found that following commit is causing
> regression for ARM.
> Though efi_flags is set with EFI_BOOT, In xen, efi_enabled() returns 0 and
> thereby boot fails with ACPI.
> Is it that runtime services are not implemented for ARM,
>  efi_flags are returning zero?.
There is already a patch on the mailing list (see [1]). Before reporting 
a bug, I would recommend you to skim through the ML to see if someone 
already report it/working on it.
Regards,

[1] <1486063532-12288-1-git-send-email-julien.grall@xxxxxxx>

> commit 146786b922ea4eeb9643029af3939244aea009c1
> Author: Daniel Kiper <daniel.kiper@xxxxxxxxxx>
> Date:   Wed Dec 7 14:36:11 2016 +0100
>
>     efi: create efi_enabled()
>
>     First of all we need to differentiate between legacy BIOS
>     and EFI platforms during runtime, not during build, because
>     one image will have legacy and EFI code and can be executed
>     on both platforms. Additionally, 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 protocol uses memory
>     mappings and loaded modules in similar way to Xen loaded by
>     multiboot (v1) protocol. Hence, create efi_enabled() which
>     checks available features in efi_flags. This patch defines
>     EFI_BOOT, EFI_LOADER and EFI_RS features. EFI_BOOT is equal
>     to old efi_enabled == 1. EFI_RS ease control on runtime
>     services usage. EFI_LOADER tells that Xen was loaded
>     directly from EFI as PE executable
>
> Regards
> Vijay
--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel