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

[Xen-devel] [PATCH 1/4] Various VT-d code cleanup

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 1/4] Various VT-d code cleanup
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Fri, 25 Jul 2008 16:32:42 +0800
Delivery-date: Fri, 25 Jul 2008 01:35:07 -0700
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: AcjuMP+AVhBn31ZnQ42QJ0ShC5YNxg==
Thread-topic: [Xen-devel] [PATCH 1/4] Various VT-d code cleanup
This patch maps RMRR in intel_iommu_add_device() if the device has RMRR;
move domain_context_mapping() to be in front of list_move() in
reassign_device_ownership().

Currently, hypervisor sets up devices and RMRR for dom0, and dom0 also
adds devices for itself via hypercall. This is obviously duplicate. In
order to allow old dom0 kernels to work with iommu-capable platforms,
maybe it cannot be removed now. But what time is suitable to solve it? 

Signed-off-by: Weidong Han <weidong.han@xxxxxxxxx>

Attachment: iommu.patch
Description: iommu.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>