Re: [PATCH v5 0/7] xen: Add EFI support

From: Konrad Rzeszutek Wilk
Date: Wed Jun 18 2014 - 10:34:01 EST


On Wed, Jun 18, 2014 at 03:15:41PM +0100, Matt Fleming wrote:
> On Fri, 13 Jun, at 07:00:16PM, Daniel Kiper wrote:
> > Hey,
> >
> > This patch series adds EFI support for Xen dom0 guests.
> > It is based on Jan Beulich and Tang Liang work. I was
> > trying to take into account all previous comments,
> > however, if I missed something sorry for that.
> >
> > Daniel
> >
> > arch/x86/kernel/setup.c | 4 +-
> > arch/x86/platform/efi/efi.c | 77 ++++++++++-------
> > arch/x86/xen/enlighten.c | 24 ++++++
> > drivers/firmware/efi/efi.c | 26 +++---
> > drivers/xen/Kconfig | 4 +
> > drivers/xen/Makefile | 3 +
> > drivers/xen/efi.c | 374 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > include/linux/efi.h | 3 +-
> > include/xen/interface/platform.h | 123 +++++++++++++++++++++++++++
> > 9 files changed, 595 insertions(+), 43 deletions(-)
>
> FWIW I'm much happier with this version than v4. There's nothing that
> jumps out at me as being obviously wrong. Just a few minor cleanups
> needed.

Fantastic!
>
> Which tree is this intended to go through? I'm more than happy to take
> it through the EFI tree, particularly since it touches
> include/linux/efi.h and drivers/firmware/efi/efi.c which is the core EFI
> interface for all platforms.

Your tree is perfect. I presume you do some automatic regression testing
when you have accumulated a tons of patch - so if any of them cause havoc
we can catch them before the merge window and fix them.

>
> But if it's going through the Xen tree or something, I can supply my
> Acked-by's (once the aforementioned minor cleanups are taken care of).

Nah, lets do your tree. And either Boris, me or David will supply
the Acked-by on the drivers/xen* and arch/x86/xen/* so all the
right tags are in place.

Thanks again!
>
> --
> Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/