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] linux/arch/xen/i386 or linux/arch/i386/xen

To: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen
From: Zachary Amsden <zach@xxxxxxxxxx>
Date: Wed, 18 May 2005 12:48:03 -0700
Cc: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, Chris Wright <chrisw@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Wed, 18 May 2005 19:48:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050518190045.GB24549@xxxxxxxxx>
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: <516F50407E01324991DD6D07B0531AD542CE25@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050518164748.GR27549@xxxxxxxxxxxxxxxxxxx> <20050518190045.GB24549@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
Vincent Hanquez wrote:

On Wed, May 18, 2005 at 09:47:48AM -0700, Chris Wright wrote:
* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@xxxxxx) 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

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

<Prev in Thread] Current Thread [Next in Thread>