From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Keir.Fraser@cl.cam.ac.uk, Christian.Limpach@cl.cam.ac.uk,
Steven.Hand@cl.cam.ac.uk, Ian.Pratt@cl.cam.ac.uk, akpm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
riel@redhat.com
Subject: Re: No Subject
Date: Wed, 15 Dec 2004 23:50:18 +0000 [thread overview]
Message-ID: <1103154617.3585.20.camel@localhost.localdomain> (raw)
In-Reply-To: <41BF1983.mailP9C1B91GB@suse.de>
The Xen interface seems to me better described that most of the kernel
interfaces and has more papers written on it. I would rather see
arch/xen and public exposure and use of the platform before considering
major redesigns. The s390 people have proved we can remove/fold arch
directories effectively and after original implementation without
problems.
I'm not convinced by your arguments about arch/xen although I am long
term in favour because I'd like see it easy to build a kernel which can
be used without Xen and can switch into Xen guest mode on Xen loading.
Alan
next prev parent reply other threads:[~2004-12-16 1:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 16:49 Andi Kleen
2004-12-15 23:50 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-30 5:02 No subject auto595907
2010-08-23 14:32 auto595907
2004-07-16 16:54 Hermann Gottschalk
2004-07-16 16:59 ` No Subject Jesse Stockall
2004-02-22 17:51 redzic fadil
2004-02-22 20:54 ` No Subject Ludootje
2003-02-21 13:43 News Admin
2003-02-21 15:01 ` No Subject Alan Cox
2002-08-05 13:08 Christos Kartsaklis
2002-08-05 14:53 ` No Subject Alan Cox
2002-08-03 19:26 Pawel Kot
2002-08-03 21:45 ` No Subject Alan Cox
2002-08-03 21:58 ` Bartlomiej Zolnierkiewicz
2002-08-03 22:16 ` Bartlomiej Zolnierkiewicz
2002-08-03 23:38 ` Alan Cox
2002-08-03 22:53 ` Bartlomiej Zolnierkiewicz
2002-08-04 13:28 ` Henning P. Schmiedehausen
2002-08-04 15:40 ` Daniela Engert
2002-08-03 23:27 ` Petr Vandrovec
2001-08-24 22:16 abraxas2
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=1103154617.3585.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox