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

Re: [Xen-devel] architecture-specific stuff in xend

On Wed, Aug 09, 2006 at 10:07:12AM -0500, Hollis Blanchard wrote:

> On Wed, 2006-08-09 at 10:28 +0100, Ewan Mellor wrote:
> > 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:
> > > 
> > > > 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
> > 
> > Platform.py:
> > 
> > import os
> > 
> > if os.uname()[4] in ('ia64', 'ppc64'):
> >     def init_reservation(mem_kb):
> >         return something_else(mem_kb)
> > 
> > else:
> >     def init_reservation(mem_kb):
> >         return mem_kb
> > 
> > and then
> > 
> > import Platform
> > Platform.init_reservation(100)
> > 
> > will do the right thing.
> 
> Ewan, does this mean you think the proposal is going in the right
> direction and you're waiting for a patch?

Yes, your proposal sounds fine to me.

Ewan.

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