[Xen-devel] [PATCH] VT-d: remove Xen and tboot range from dom0's

To:	<xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] VT-d: remove Xen and tboot range from dom0's VT-d table
From:	"Yang, Xiaowei" <xiaowei.yang@xxxxxxxxx>
Date:	Fri, 23 May 2008 15:56:19 +0800
Delivery-date:	Fri, 23 May 2008 01:04:59 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	Aci8qnw6NjVqOC1KRmqCa/IxrhLv/Q==
Thread-topic:	[PATCH] VT-d: remove Xen and tboot range from dom0's VT-d table

This a step forward to fix the security hole introduced by dom0's 1:1
mapping VT-d table: remove the critical code and data from it. The more
flexible solution is to update dom0's VT-d table on demand as what will
be done for other PV domains. However, there could bring a performance
issue even with software optimization. Iotlb flush of some hardware is
time-consuming.

Signed-off-by: Yang, Xiaowei <xiaowei.yang@xxxxxxxxx>

Thanks,
Xiaowei

vtd_protect.patch
Description: vtd_protect.patch

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH] VT-d: remove Xen and tboot range from dom0's VT-d ta