From: Andi Kleen <ak@suse.de>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Xen 2.0 VMM patches
Date: Thu, 18 Nov 2004 14:22:33 +0100 [thread overview]
Message-ID: <20041118132233.GG17532@wotan.suse.de> (raw)
In-Reply-To: <E1CUjSB-0005II-00@mta1.cl.cam.ac.uk>
On Thu, Nov 18, 2004 at 10:23:50AM +0000, Ian Pratt wrote:
> 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.
2.6 has been relatively easy for now (because it was supposed
to be a "stable kernel"), but I suspect it'll get worse again over time.
e.g. in 2.5 it was really bad for long times.
Essentially you will need to commit significant man power to this.
Also it's quite hard to always catch all the changes that
get done to i386.
Overall I think it's a bad idea to have four different
x86 like architectures in the tree. Especially since there
will be likely more hypervisors over time. i386 and x86-64 make
some sense because 64bit is a natural boundary, but extending
it elsewhere doesn't scale very well.
-Andi
next prev parent reply other threads:[~2004-11-18 17:08 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
2004-11-18 13:22 ` Andi Kleen [this message]
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=20041118132233.GG17532@wotan.suse.de \
--to=ak@suse.de \
--cc=Ian.Pratt@cl.cam.ac.uk \
--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
Powered by JetHome