[Xen-devel] iommu=1 by default?

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Subject:	[Xen-devel] iommu=1 by default?
From:	Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Date:	Tue, 19 Jan 2010 09:59:16 +0000
Accept-language:	en-US
Acceptlanguage:	en-US
Cc:	Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date:	Tue, 19 Jan 2010 02:00:47 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcqY7g/TEKaJIVD9RCySPimgFxvgDA==
Thread-topic:	iommu=1 by default?

Would it make sense to make "iommu=1" the default for xen 4.0?

I think Xen is rather more defensive these days about disabling iommu in the 
presence of broken BIOS tables, but there may conceivably still be machines it 
breaks boot on. I can't think of any subtle bugs the IOMMU could introduce if 
it's not explicitly in use by VMs -- and I don't believe anyone has seen any 
performance issues. [We could actually not fully turn the IOMMU on until the 
first VM that demands it.]

Would it make sense to turn it on by default in the release candidates? Or too 
late? 

IOMMU is clearly going to be a widely used feature in this release.

Ian

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] iommu=1 by default?