[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Transparent paravirtualization vs. xen paravirtualization (was:RE: [Xen-ia64-devel] IRQ management)

  • To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Tue, 25 Oct 2005 19:53:05 -0700
  • Delivery-date: Wed, 26 Oct 2005 02:50:20 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXZOp796DRvjoa4Quuc0MiGEhv36AAi6iuwAARQzfA=
  • Thread-topic: Transparent paravirtualization vs. xen paravirtualization (was:RE: [Xen-ia64-devel] IRQ management)
>       Another thing like IOAPCI as Kevin pointed out is a 
> must to be in HV as driver domain in future must have this 
> feature.

Driver domains are still not supported in Xen/x86 for 3.0.
There have been one or two designs proposed but none
yet implemented.  I've been delaying any design work
on Xen/ia64 driver domains until we see what happens
with Xen/x86.

Dan

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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.