All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Cc: "Magenheimer,
	Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
	Chris Wright <chrisw@osdl.org>,
	xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen
Date: Wed, 18 May 2005 12:48:03 -0700	[thread overview]
Message-ID: <428B9BF3.70408@vmware.com> (raw)
In-Reply-To: <20050518190045.GB24549@snarc.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

  reply	other threads:[~2005-05-18 19:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 15:09 linux/arch/xen/i386 or linux/arch/i386/xen Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 16:47 ` Chris Wright
2005-05-18 19:00   ` Vincent Hanquez
2005-05-18 19:48     ` Zachary Amsden [this message]
2005-05-18 20:31       ` Vincent Hanquez
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19 17:18 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-19 18:55 ` Chris Wright
2005-05-18 19:21 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:00 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:17 ` Chris Wright
2005-05-18 18:35   ` Zachary Amsden
2005-05-17 19:05 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 18:09 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 18:14 ` Chris Wright
2005-05-18 10:15   ` Vincent Hanquez
2005-05-18 16:53     ` Chris Wright
2005-05-18 18:56       ` Vincent Hanquez
2005-05-17 17:25 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 17:58 ` Chris Wright
2005-05-18 18:20   ` Christian Limpach
2005-05-16 22:42 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:50 ` Mark Williamson
2005-05-16 23:22   ` Chris Wright
2005-05-16 21:37 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:21 ` Mark Williamson
2005-05-16 17:36 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 18:07 ` Chris Wright

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=428B9BF3.70408@vmware.com \
    --to=zach@vmware.com \
    --cc=chrisw@osdl.org \
    --cc=dan.magenheimer@hp.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=vincent.hanquez@cl.cam.ac.uk \
    --cc=xen-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.