mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
To: Andi Kleen <ak@suse.de>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	linux-kernel@vger.kernel.org, Ian.Pratt@cl.cam.ac.uk
Subject: Re: Xen 2.0 VMM patches
Date: Thu, 18 Nov 2004 10:23:50 +0000	[thread overview]
Message-ID: <E1CUjSB-0005II-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "18 Nov 2004 05:50:54 +0100." <p73k6sj221d.fsf@brahms.suse.de>

> Ian Pratt <Ian.Pratt@cl.cam.ac.uk> writes:
> 
> >   arch-xen    : large patch to add arch/xen and include/asm-xen 
> 
> This is 32bit only right? Do you plan a 64bit guest too? 
> If yes, you would end up with two arch-xens in the end.

We have an x86_64 guest port in progress, hence the current
directory structure below arch/xen. There's a fair bit of
arch/xen-specific code that we can share between the ports.

> Also are the differences to the native architecture really that big that a 
> separate architecture makes sense? It's a lot of long term work to maintain
> a Linux architecture.

We've experimented with doing thing the other way round, having
xen a sub architecture of i386, but it was _really_ messy.

I firmly believe that having a separate arch/xen is the best
approach for the moment. In the future, it might make sense to
merge arch xen into i386, but to do this cleanly would require
significant restructuring of i386. I think that's something we
could move toward after everyone's gotten comfortable with having
arch xen in the tree. 

The fact that arch xen is self contained actually makes it easier
for us to maintain in some respects. We've been tracking 2.6
releases for some time without too much difficulty.


Best,
Ian


  reply	other threads:[~2004-11-18 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <31IYf-4Y-5@gated-at.bofh.it>
2004-11-18  4:50 ` Andi Kleen
2004-11-18 10:23   ` Ian Pratt [this message]
2004-11-18 13:22     ` Andi Kleen
2004-11-18 17:26       ` Roland Dreier
2004-11-18 17:38         ` Ian Pratt
2004-11-17 23:43 Ian Pratt
2004-11-18  6:59 ` Pekka Enberg
2004-11-18  7:03   ` Pekka Enberg
2004-11-18 21:37 ` Bill Davidsen

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=E1CUjSB-0005II-00@mta1.cl.cam.ac.uk \
    --to=ian.pratt@cl.cam.ac.uk \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®