WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: A proposal - binary

To: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: A proposal - binary
From: David Lang <dlang@xxxxxxxxxxxxxxxxxx>
Date: Fri, 4 Aug 2006 12:45:50 -0700 (PDT)
Cc: Andrew Morton <akpm@xxxxxxxx>, zach@xxxxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy@xxxxxxxxxxxxx, simon@xxxxxxxxxxxxx, jlo@xxxxxxxxxx, greg@xxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Antonio Vargas <windenntw@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxxx, torvalds@xxxxxxxx
Delivery-date: Mon, 07 Aug 2006 02:20:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44D39F73.8000803@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44D1CC7D.4010600@xxxxxxxxxx> <20060803190605.GB14237@xxxxxxxxx> <44D24DD8.1080006@xxxxxxxxxx> <20060803200136.GB28537@xxxxxxxxx> <44D2B678.6060400@xxxxxxxxxxxxx> <20060803211850.3a01d0cc.akpm@xxxxxxxx> <1154667875.11382.37.camel@xxxxxxxxxxxxxxxxxxxxx> <20060803225357.e9ab5de1.akpm@xxxxxxxx> <1154675100.11382.47.camel@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.63.0608040944480.18902@xxxxxxxxxxxxxxxxxxx> <69304d110608041146t44077033j9a10ae6aee19a16d@xxxxxxxxxxxxxx> <Pine.LNX.4.63.0608041150360.18862@xxxxxxxxxxxxxxxxxxx> <44D39F73.8000803@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 4 Aug 2006, Arjan van de Ven wrote:

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.

so if I understand this correctly we are saying that a kernel compiled to run on hypervisor A would need to be recompiled to run on hypervisor B, and recompiled again to run on hypervisor C, etc

where A could be bare hardware, B could be Xen 2, C could be Xen 3, D could be vmware, E could be vanilla Linux, etc.

this sounds like something that the distros would not support, they would pick their one hypervisor to support and leave out the others. the big problem with this is that the preferred hypervisor will change over time and people will be left with incompatable choices (or having to compile their own kernels, including having to recompile older kernels to support newer hypervisors)

David Lang



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel