[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH V4 02/15] Move x86 specific funtions/variables to arch header

On Fri, 2014-09-12 at 08:04 +0100, Jan Beulich wrote:
> > This does scanning of PCI ROMS, which is unlikely to do anything
> > useful on ARM platforms.
> Why not? Obviously if the ROMs contain x86 code, they're useless,
> but in order to, say, do remote boot I suppose you need option
> ROMs (with ARM code) on ARM too.

Doesn't that all happen at the UEFI layer, long before Xen gets
involved, even on x86?

Does Xen itself do network boot/loading or does it call some UEFI layer?

> > I also have no way to test this on ARM.
> > I can try to pull this back in, but I may run into dependency issues
> > such as those with VGA, where I did not
> > want to pull in otherwise unused (and likely unusable on ARM)
> > drivers/subsystems in order to keep a little more
> > code in the common EFI boot path.
> The base line should be too keep everything here that is potentially
> usable on more than one arch (without limiting our thinking to ARM
> and x86). EFI's protocol based approach abstracts this quite nicely
> - if something isn't available, you simply won't find th respective
> protocol.

Irrespective of the above this seems like a sensible approach.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.