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: Hollis Blanchard <hollisb@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] [LIBXC] add architecture-specific parameter to xc_linux_build()
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 09 Aug 2006 17:44:22 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 09 Aug 2006 09:45:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1155136470.2821.12.camel@diesel>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aca70xC9T1BpUCfGEduK+AAKle7CWA==
Thread-topic: [Xen-devel] Re: [PATCH] [LIBXC] add architecture-specific parameter to xc_linux_build()
User-agent: Microsoft-Entourage/

On 9/8/06 4:14 pm, "Hollis Blanchard" <hollisb@xxxxxxxxxx> wrote:

> 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?

Hmmm... I was expecting you'd want a ppc-specific libxenguest or libxenctrl
function, but I guess maybe you could do it by more generic means. That
would obviously be much preferable if it's possible.

Could a copy_to/from_guest interface exposed to Python be used? Or does the
device tree need some processing in C into an appropriate format for writing
into guest memory? As for set/get_vcpu_context, the context could be
expressed as a Python dictionary mapping register names to (reasonably
constrained) long values.

 -- Keir

Xen-devel mailing list