On Wed, Jun 18, 2014 at 03:30:25PM +0100, Stefano Stabellini wrote: > On Wed, 18 Jun 2014, Jan Beulich wrote: > > >>> On 18.06.14 at 15:52, <matt@xxxxxxxxxxxxxxxxx> wrote: > > > EFI_PARAVIRT will be usable by architectures other than x86, correct? If > > > your intention is for it only ever to be used by x86, then it should > > > probably be EFI_ARCH_2. > > > > I would expect ARM, once it gets UEFI support on the Xen side, to > > be able to handle most of this identically to x86. Which raises the > > question whether most of the new Xen-specific code (in one of the > > other patches) wouldn't better live under drivers/xen/. > > I was thinking the same thing. > > However this patch series doesn't add much code outside > drivers/xen/efi.c and include/xen/interface/platform.h. > I think it wouldn't be fair to ask Daniel to refactor the efi code > currently under arch/x86 to an arch-independent location. > Whoever comes in later and adds EFI Xen support for ARM can do that. I was doing those EFI patches with ARM support in mind from the beginning. That is why I moved everything, which was possible, to arch independent place. There are only some simple init calls from arch/x86. Just a few required lines. So I think that it will be quite easy to use this EFI code on ARM platform. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
