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

Re: [Xen-devel] Re: [PATCH] [LIBXC] add architecture-specific parameter to xc_linux_build()



On Wed, 2006-08-09 at 11:16 +0100, Keir Fraser wrote:
> 
> Actually I'm not sure about this approach at all. Couldn't specifying the
> open firmware tree be done separately from the build (e.g., just after)?
> Maybe hooked off the new proposed 'platform object' in xend. Xc_linux_build
> is really ugly enough already: I think in future we would like to split
> xc_linux_build up into smaller API functions, even for x86, and that the
> patch you propose goes in the opposite direction to this.

That direction certainly seems like a good one to me.

In this case, we need to load the device tree into the domain's memory
and pass its address in a register (i.e. via xc_vcpu_setcontext).
Currently it doesn't look like xc_vcpu_setcontext is exposed to python
for us to use. What would you like to see here?

-- 
Hollis Blanchard
IBM Linux Technology Center


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


 


Rackspace

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