Re: [Xen-devel] [PATCH v5 10/16] efi: create efi_enabled()

2016-08-31 Thread Jan Beulich
>>> On 30.08.16 at 19:19, wrote: > On Thu, Aug 25, 2016 at 06:16:35AM -0600, Jan Beulich wrote: >> >>> On 20.08.16 at 00:43, wrote: >> > --- a/xen/arch/x86/efi/stub.c >> > +++ b/xen/arch/x86/efi/stub.c >> > @@ -4,9 +4,10 @@ >> > #include >> >

Re: [Xen-devel] [PATCH v5 10/16] efi: create efi_enabled()

2016-08-30 Thread Daniel Kiper
On Thu, Aug 25, 2016 at 06:16:35AM -0600, Jan Beulich wrote: > >>> On 20.08.16 at 00:43, wrote: > > --- a/xen/arch/x86/efi/stub.c > > +++ b/xen/arch/x86/efi/stub.c > > @@ -4,9 +4,10 @@ > > #include > > #include > > > > -#ifndef efi_enabled > > -const bool_t

Re: [Xen-devel] [PATCH v5 10/16] efi: create efi_enabled()

2016-08-25 Thread Jan Beulich
>>> On 20.08.16 at 00:43, wrote: > --- a/xen/arch/x86/efi/stub.c > +++ b/xen/arch/x86/efi/stub.c > @@ -4,9 +4,10 @@ > #include > #include > > -#ifndef efi_enabled > -const bool_t efi_enabled = 0; > -#endif > +bool_t efi_enabled(int feature) > +{ > +return false;

[Xen-devel] [PATCH v5 10/16] efi: create efi_enabled()

2016-08-19 Thread Daniel Kiper
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