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] About VT-d on ASUS P6T

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] About VT-d on ASUS P6T
From: Felix Kuperjans <felix@xxxxxxxxxxxxxxxxxx>
Date: Tue, 11 May 2010 12:09:27 +0200
Delivery-date: Tue, 11 May 2010 03:10: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
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100413 Shredder/3.0.4
Hi,

as I posted on xen-users, I've successfully used pci passtrough on an ASUS P6T 
mainboard which is known to have really buggy RMRR tables.

I needed the iommu=passtrough and iommu_inclusive_mapping=1 command line 
options, combined with a little change to the RMRR parsing code:

dmar.c:

@@ -559,8 +558,7 @@
             dprintk(XENLOG_WARNING VTDPREFIX,
                 "  The RMRR (%"PRIx64", %"PRIx64") is incorrect!\n",
                 rmrru->base_address, rmrru->end_address);
-            xfree(rmrru);
-            ret = -EFAULT;
+            acpi_register_rmrr_unit(rmrru);
         }
         else
         {

This way, the condition that causes the error printed above, does not lead to 
an abortion of VT-d code, but instead registers the RMRR unit as if it was 
correct.
VT-d is working properly afterwards and I've tested some devices successfully.

Probably, you would prefer to choose the action based on some command line 
option (like iommu_inclusive_mapping=1) instead of ignoring this error by 
default.

Regards,
Felix


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

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