[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090603094753.6eb32099@lxorguk.ukuu.org.uk>
Date: Wed, 3 Jun 2009 09:47:53 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Gerd Hoffmann <kraxel@...hat.com>
Cc: Theodore Tso <tytso@....edu>,
Dan Magenheimer <dan.magenheimer@...cle.com>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
George Dunlap <george.dunlap@...citrix.com>,
David Miller <davem@...emloft.net>, jeremy@...p.org,
avi@...hat.com, xen-devel@...ts.xensource.com, x86@...nel.org,
linux-kernel@...r.kernel.org,
Keir Fraser <Keir.Fraser@...citrix.com>,
torvalds@...ux-foundation.org, gregkh@...e.de,
kurt.hackel@...cle.com, Ian Pratt <Ian.Pratt@...citrix.com>,
xen-users@...ts.xensource.com,
ksrinivasan <ksrinivasan@...ell.com>, EAnderson@...ell.com,
wimcoekaerts@...mekes.net,
Stephen Spector <stephen.spector@...rix.com>,
jens.axboe@...cle.com, npiggin@...e.de
Subject: Re: Merge Xen (the hypervisor) into Linux
> Linux is not the only player here. NetBSD can run as dom0 guest.
> Solaris can run as dom0 guest too. Thus making the dom0/xen interface
> private to linux and xen isn't going to fly.
It does not however preclude fixing the dom0 interface.
Anyway we deal with unfixable interfaces on a regular basis with device
hardware. What we don't do is screw up the kernel handling garbage
hardware. We dump the adaption on the driver.
Same with Xen, impedance matching Xen's interface with the kernel is (at
least initialy) something that belongs entirely in the Xen glue, or to
get started initially by just turning off stuff.
MTRR, PAE etc can all be turned off for the purpose an initial merge.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists