From: John Levon <levon@movementarian.org>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-ppc-devel <xen-ppc-devel@lists.xensource.com>,
xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: [XenPPC] Re: [Xen-devel] architecture-specific stuff in xend
Date: Tue, 8 Aug 2006 16:59:53 +0100 [thread overview]
Message-ID: <20060808155953.GA20410@totally.trollied.org> (raw)
In-Reply-To: <1155051266.30116.152.camel@basalt.austin.ibm.com>
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?
regards
john
next prev parent reply other threads:[~2006-08-08 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 15:34 architecture-specific stuff in xend Hollis Blanchard
2006-08-08 15:59 ` John Levon [this message]
2006-08-08 16:15 ` Hollis Blanchard
2006-08-08 17:12 ` John Levon
2006-08-09 9:28 ` Ewan Mellor
2006-08-09 15:07 ` Hollis Blanchard
2006-08-09 16:18 ` Ewan Mellor
2006-08-10 21:12 ` [PATCH] " Hollis Blanchard
2006-08-10 21:27 ` John Levon
2006-08-11 22:59 ` Daniel Miles
2006-08-14 17:40 ` Hollis Blanchard
2006-08-15 2:14 ` Hollis Blanchard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060808155953.GA20410@totally.trollied.org \
--to=levon@movementarian.org \
--cc=ewan@xensource.com \
--cc=hollisb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.