linux-kernel - Re: Merge Xen (the hypervisor) into Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090603111541.GC31943@mit.edu>
Date:	Wed, 3 Jun 2009 07:15:41 -0400
From:	Theodore Tso <tytso@....edu>
To:	Gerd Hoffmann <kraxel@...hat.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	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

On Wed, Jun 03, 2009 at 11:09:39AM +0200, Gerd Hoffmann wrote:
> On 06/03/09 10:47, Alan Cox wrote:
>>> 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.
>
> It wasn't my intention to imply that.  The interface can be extended  
> when needed.  PAT support will probably be such a case.  Changing it in  
> incompatible ways isn't going to work though.

But that means that if there is some fundamentally broken piece of
dom0 design, that the Linux kernel will be stuck with it ***forever***
and it will contaminate code paths and make the code harder to
maintain ***forever*** if we consent to the Xen merge?  Is that really
what you are saying?   Be careful how you answer that....

     	     	       	  	      	  - Ted
--
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/