From: Chris Wright Subject: Re: [RFC, PATCH 5/24] i386 Vmi code patching Date: Wed, 22 Mar 2006 16:41:36 -0800 Message-ID: <20060323004136.GR15997@sorel.sous-sol.org> References: <200603131802.k2DI2nv8005665@zach-dev.vmware.com> <200603222115.46926.ak@suse.de> <20060322214025.GJ15997@sorel.sous-sol.org> <4421CCA8.4080702@vmware.com> <20060322225117.GM15997@sorel.sous-sol.org> <4421DF62.8020903@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4421DF62.8020903@vmware.com> Sender: linux-kernel-owner@vger.kernel.org To: Zachary Amsden Cc: Chris Wright , Andi Kleen , virtualization@lists.osdl.org, Linus Torvalds , Linux Kernel Mailing List , Xen-devel , Andrew Morton , Dan Hecht , Dan Arai , Anne Holler , Pratap Subrahmanyam , Christopher Li , Joshua LeVasseur , Rik Van Riel , Jyothy Reddy , Jack Lo , Kip Macy , Jan Beulich , Ky Srinivasan , Wim Coekaerts , Leendert van Doorn List-Id: xen-devel@lists.xenproject.org * Zachary Amsden (zach@vmware.com) wrote: > Chris Wright wrote: > >You could compile all platform layers you want to support with the kernel. > > But the entire point is that you don't know what platform layers you > want to support. The platform layers can change. Xen has changed the > platform layer and re-optimized kernel / hypervisor transitions how many > times? The platform layer provides exactly the flexibility to do that, > so that a kernel you compile today against a generic platform can work > with the platform layer provided by Xen 4.0 tomorrow. This only works if you have all possible dreamed of interface bits in the ABI. In Linux, we often don't know what we'll need to support in the future, but we don't write binary compatible interfaces just in case we need to update. Preferring instead, API's that are justifiable right now. This is the issue I have with the ABI proposal. It doesn't fit well with Linux developement. thanks, -chris