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] Xen as a kernel module

To: Tobias Hunger <tobias@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen as a kernel module
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Fri, 28 Jan 2005 12:09:42 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 29 Jan 2005 00:25:31 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <200501271605.19343.tobias@xxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1Ctijw-0004J6-00@xxxxxxxxxxxxxxxxx> <41F8257E.608@xxxxxxx> <200501271605.19343.tobias@xxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20050116)
Tobias Hunger wrote:

Right now Xen is mapped somewhere in top of memory, I am not sure how
domains are kept out of there, but I suppose it has to do with segments.


As I understand this xen runs in ring0 and pushes the guests kernels one ring up into ring1 and then uses traps to allow the guest OSes to trap into the hypervisor as necessary.


The good thing about that is that hypercalls are cheap, and in Xen1.x
I/O was cheap as well.


Cheap where? In dom0 or the VMs?

Both. Assuming that context switching is an expensive operation, and that most of the cost comes from flushing the TLBs, the current model has more overhead than a model where the drivers are mapped into the same address space (though still protected from domU access other that through hypercalls) as the currently running domain. Xen already contains magic that allows it to be permanently mapped into running domains, while still being protected from accidential/malicious access.

I am calling that monolithic, because that is what standard linux does, and what the old Xen 1.x did. The current model is more like a microkernel, such as L4 or Mach (though of course a lot more clever, no offense people ;-))

Apart from perhaps increasing performance, I was saying it would be cool if the Xen-interface could be provided on platforms such as Windows or native Linux. People have done similar stuff before (e.g. VMWare vmmon, the Adeos nanokernel, coLinux), so it should be possible. It seems Xen would have better chances of world domination that way, if that is a goal. It would also save some duplication of effort in porting guestOSes to the different models out there.

Anyway, it was just an idea, and it is likely that with future hardware the Xen NGIO/microkernel model will finally be overhead-free, vendors will start writing Xen-VM drivers, and we will all live happily ever after :-).

Jacob


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>