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] architecture-specific stuff in xend

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] architecture-specific stuff in xend
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Wed, 9 Aug 2006 10:28:10 +0100
Cc: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 09 Aug 2006 02:28:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060808155953.GA20410@xxxxxxxxxxxxxxxxxxxx>
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>
References: <1155051266.30116.152.camel@xxxxxxxxxxxxxxxxxxxxx> <20060808155953.GA20410@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Aug 08, 2006 at 04:59:53PM +0100, John Levon wrote:

> On Tue, Aug 08, 2006 at 10:34:25AM -0500, Hollis Blanchard wrote:
> > Rather than having these inline tests everywhere ("if os.uname()[4] in
> > ('ia64', 'ppc64'):"), would it make more sense to have some sort of
> > "architecture" object, and do things like:
> It'd be good if it were slightly more general and covered other system
> stuff too (namely OS). On Solaris some of the Xen binaries/scripts live
> in different locations in order to meet our file system requirements.
> > I'm not sure how/where to instantiate the arch object though.
> Presumably you could do the instance() singleton trick?

This being Python, you don't actually need singletons -- the containing module
is a singleton in its own right.  You can just write


import os

if os.uname()[4] in ('ia64', 'ppc64'):
    def init_reservation(mem_kb):
        return something_else(mem_kb)

    def init_reservation(mem_kb):
        return mem_kb

and then

import Platform

will do the right thing.


Xen-devel mailing list