From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen Date: Wed, 18 May 2005 12:48:03 -0700 Message-ID: <428B9BF3.70408@vmware.com> References: <516F50407E01324991DD6D07B0531AD542CE25@cacexc12.americas.cpqcorp.net> <20050518164748.GR27549@shell0.pdx.osdl.net> <20050518190045.GB24549@snarc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20050518190045.GB24549@snarc.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , Chris Wright , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org Vincent Hanquez wrote: >On Wed, May 18, 2005 at 09:47:48AM -0700, Chris Wright wrote: > > >>* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote: >> >> >>>Um, one other minor semantic issue. The semantics of >>>using mach-xxx may be inappropriate. If my understanding >>>is correct, two mach-xxx's cannot both be built, e.g. one >>>cannot build a kernel which supports (for i386) both >>>mach-es7000 and mach-voyager. >>> >>> >>Yes, I had thought about this. It's not clear to me it's problematic yet. >> >> > >I guess it could be, as if I understood correctly Keir's later post, we >would like to run on other subarch. > > I see, you would like domain zero to support other subarchs? I guarantee you it is not going to be voyager! There should be no issue for user domains, but could domain zero could potentially need to know things about the hardware subarch, say for some large NUMA systems? Zach