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

Re: [Xen-devel] Re: Pre-virtualization, was Re: linux/arch/xen/i386 or l

To: "Ronald G. Minnich" <rminnich@xxxxxxxx>
Subject: Re: [Xen-devel] Re: Pre-virtualization, was Re: linux/arch/xen/i386 or linux/arch/i386/xen
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Fri, 20 May 2005 13:32:33 -0500
Cc: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 May 2005 18:32:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0505201154350.28152@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: <516F50407E01324991DD6D07B0531AD542CF64@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <03B0FCC6-50E1-45DF-A24F-B35518AD068D@xxxxxxxxxx> <9cde8bff05052010231c0b0d29@xxxxxxxxxxxxxx> <Pine.LNX.4.58.0505201154350.28152@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
Ronald G. Minnich wrote:

On Sat, 21 May 2005, aq wrote:
Joshua, as I understand, this project would be a competitor of Xen?
http://l4hq.org/cvsweb/cvsweb/~checkout~/afterburner/afterburn-wedge/doc/userman.pdf?content-type=application/pdf

for the manual.

You still have to modify the kernel, it seems.
Strictly speaking you should be able to achieve "full virtualization" with toolchain modifications. Think of the comparision to VMX. VMX provides exits to call into the hypervisor when certain instructions are executed that are not virtualization friendly. With pre-virtualization, you have the compiler pad virtualization unfriendly instructions with nop's and then at load time, replace all of those unfriendly sequences with calls to the hypervisor. This way, the same kernel can run on bare metal or within a hypervisor.
Of course, just as is likely with VMX, you're probably gonna want to do 
some hand-tuning of Linux for performance reasons.  It seems like 
afterburner incorporates these types of optimizations.
I'd really like to see a "pure" form of pre-virtualization that required 
no modifications at all to the underlying source tree.  Besides being 
interesting from an academic standpoint I think it would be highly 
useful for support legacy Open Source operating systems.
I'm very excited about this technology.  I imagine that you can get all 
the benefits of binary-rewriting with less complexity and better 
performance (with the only limitation being that you have the source 
code for the OS which is fine by me).
Regards,
Anthony Liguori

Are there fewer mods? What is the advantage of this over Xen? I think I'm missing a key point here.
ron

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


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