On Sun, Aug 05, 2012 at 10:05:00AM +0200, Lukas Hejtmanek wrote: > Hi, > > On Fri, Aug 03, 2012 at 06:49:59AM -0700, Konrad Wilk wrote: > > This looks like you are using PV PCI passthrough? If so, did you > > remember to use 'iommu=soft' to enable the Xen-SWIOTLB in your guest? > > And are you booting with more than 4GB? Or is less than 3GB (so that you have > > a nice gap in E820). > > good catch. I forgot to pass swiotl=force for DomU in Xen. So now, it seems > that mlx4_core works, mlx4_en (ethernet part) works as well. Unfortunately, > the IB part does not. IB layer complains that SR-IOV is currently unsupported > (kernel 3.5.0). So no luck here so far. Don't use swiotlb=force. That is for the old style kernels. Use iommu=soft. > > There is OFED stack directly from Mellanox, that seems to support SR-IOV even > for IB layer, but they have buildable sources only for RHEL/SLES kernels > (2.6.32) and even correcting the sources to get it compile with 3.5.0 does not > make things work. The driver complains about interrupts not working in Dom0 or > even without Xen hypervisor at all. So there is a bug that .. well, I thought I had fixed it with the IB layer but maybe not. It was about VM_IO having to be used on the vmaps being setup. But I can't recall the details. Perhaps the InfiniBand mailing list might have some ... ah here it is: http://old-list-archives.xen.org/archives/html/xen-devel/2011-01/msg00246.html > > The only good point is, that I managed to convice Supermicro (board > manufacturer), that enabling SR-IOV in BIOS leads to BIOS lockup, they > confirmed it and maybe they provide BIOS upgrade. > > Thanks all. > > -- > Lukáš Hejtmánek -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
