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/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH] [LIBXC] add architecture-specific parameter

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] [LIBXC] add architecture-specific parameter to xc_linux_build()
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Wed, 09 Aug 2006 10:14:30 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 09 Aug 2006 08:15:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C0FF749A.AE9%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <C0FF749A.AE9%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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