| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] architecture-specific stuff in xend
On Tue, Aug 08, 2006 at 11:15:18AM -0500, Hollis Blanchard wrote:
> > On Solaris some of the Xen binaries/scripts live
> > in different locations in order to meet our file system requirements.
>
> Does that impact code under tools/python/xen much?
Very little, but it does affect the location of the network scripts, for
example.
> > Presumably you could do the instance() singleton trick?
>
> Not sure what you mean.
See XendRoot.py's instance().
> Actually, you bring up a good point: since we have no state (at least
> not in the examples I'm thinking of), we really don't want/need a class;
> a module would do just fine. So we could have separate files/modules
> with just plain functions:
>
> platform/ia64.py:
> def init_reservation(mem_kb):
> return something
>
> platform/platform.py:
> import xen.xend.platform.ia64 as platform
We'd still need something to import the right bits...
regards
john
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home