Re: [PATCH v5 4/7] xen: Put EFI machinery in place

2014-06-16 Thread Daniel Kiper
On Mon, Jun 16, 2014 at 01:00:29PM +0100, David Vrabel wrote: > On 13/06/14 18:00, Daniel Kiper wrote: > > > > v5 - suggestions/fixes: > > Put after a --- marker. Why? You mean: --- v5 - suggestions/fixes: ... > > +static efi_char16_t vendor[100] __initdata; > > Why 100? Well... Quite arbitra

Re: [PATCH v5 4/7] xen: Put EFI machinery in place

2014-06-16 Thread Daniel Kiper
On Mon, Jun 16, 2014 at 12:55:35PM +0100, Stefano Stabellini wrote: > On Fri, 13 Jun 2014, Daniel Kiper wrote: > > This patch enables EFI usage under Xen dom0. Standard EFI Linux > > Kernel infrastructure cannot be used because it requires direct > > access to EFI data and code. However, in dom0 ca

Re: [PATCH v5 4/7] xen: Put EFI machinery in place

2014-06-16 Thread David Vrabel
On 13/06/14 18:00, Daniel Kiper wrote: > > v5 - suggestions/fixes: Put after a --- marker. > +static efi_char16_t vendor[100] __initdata; Why 100? David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordo

Re: [PATCH v5 4/7] xen: Put EFI machinery in place

2014-06-16 Thread Stefano Stabellini
On Fri, 13 Jun 2014, Daniel Kiper wrote: > This patch enables EFI usage under Xen dom0. Standard EFI Linux > Kernel infrastructure cannot be used because it requires direct > access to EFI data and code. However, in dom0 case it is not possible > because above mentioned EFI stuff is fully owned and

[PATCH v5 4/7] xen: Put EFI machinery in place

2014-06-13 Thread Daniel Kiper
This patch enables EFI usage under Xen dom0. Standard EFI Linux Kernel infrastructure cannot be used because it requires direct access to EFI data and code. However, in dom0 case it is not possible because above mentioned EFI stuff is fully owned and controlled by Xen hypervisor. In this case all c