From: Arjan van de Ven Subject: Re: A proposal - binary Date: Fri, 04 Aug 2006 12:26:43 -0700 Message-ID: <44D39F73.8000803@linux.intel.com> References: <44D1CC7D.4010600@vmware.com> <20060803190605.GB14237@kroah.com> <44D24DD8.1080006@vmware.com> <20060803200136.GB28537@kroah.com> <44D2B678.6060400@xensource.com> <20060803211850.3a01d0cc.akpm@osdl.org> <1154667875.11382.37.camel@localhost.localdomain> <20060803225357.e9ab5de1.akpm@osdl.org> <1154675100.11382.47.camel@localhost.localdomain> <69304d110608041146t44077033j9a10ae6aee19a16d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: David Lang Cc: Antonio Vargas , Rusty Russell , Andrew Morton , jeremy@xensource.com, greg@kroah.com, zach@vmware.com, linux-kernel@vger.kernel.org, torvalds@osdl.org, hch@infradead.org, jlo@vmware.com, xen-devel@lists.xensource.com, simon@xensource.com, ian.pratt@xensource.com, jeremy@goop.org List-Id: xen-devel@lists.xenproject.org David Lang wrote: > I'm not commenting on any of the specifics of the interface calls (I > trust you guys to make that be sane :-) I'm just responding the the idea > that the interface actually needs to be locked down to an ABI as opposed > to just source-level compatability. you are right that the interface to the HV should be stable. But those are going to be specific to the HV, the paravirt_ops allows the kernel to smoothly deal with having different HV's. So in a way it's an API interface to allow the kernel to deal with multiple different ABIs that exist today and will in the future.