|
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 15:45:33 -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:27:50 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<44D3C37F.7020803@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> <Pine.LNX.4.63.0608041239430.18862@xxxxxxxxxxxxxxxxxxx> <44D3C37F.7020803@xxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Fri, 4 Aug 2006, Arjan van de Ven wrote:
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
no the actual implementation of the operation structure is dynamic and can be
picked
at runtime, so you can compile a kernel for A,B *and* C and at runtime the
kernel
picks the one you have
Ok, I was under the impression that this sort of thing was frowned upon for
hotpath items (which I understand a good chunk of this would be).
this still leaves the question of old client on new hypervisors that is
continueing in other branches of this thread.
David Lang
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home