WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [XenPPC] [PATCH] default link address

On Fri, Jun 16, 2006 at 04:45:19PM -0400, Michal Ostrowski wrote:
> Perhaps we should, like Linux does, run early code to interface with FW
> in a relocatable manner (perhaps even as a separately linked program)
> and once we kill FW then we locate the HV code at any place we want.
> 
> Moving link addresses to accommodate a particular FW version means that
> we may end up clashing with another instance of FW.
> 
> Such early FW-interface code would produce a Linux compatible DTC; and
> Xen itself should only depend on that.  This will allow Xen to run on
> any platform that supports Linux -- and note that platforms may support
> Linux not by providing an actual OF instance, but rather by providing a
> a DTC blob.
> 
> This would also allow us to play nice with kexec, which as a bonus would
> allow for a scenario where we boot a Linux to do initial system set-up
> and then kexec into Xen.   

This might be something we want to get involved in.  Check out the kboot
project, they have a paper here and are presenting at OLS:

 http://kboot.sourceforge.net/

Note that K42 will just work with kboot when/if it supports PPC64, it
wasn't that hard to do.  I think it would save Xen a lot of maintenence
work down the road.


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel

<Prev in Thread] Current Thread [Next in Thread>