Hi Bart, > -----Original Message----- > From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma- > owner@xxxxxxxxxxxxxxx] On Behalf Of Bart Van Assche > Sent: Friday, March 3, 2017 4:05 PM > To: Parav Pandit <parav@xxxxxxxxxxxx>; loberman@xxxxxxxxxx > Cc: linux-rdma@xxxxxxxxxxxxxxx; dledford@xxxxxxxxxx > Subject: Re: v4.11 mlx5 regression > > On Tue, 2017-02-28 at 20:34 +0000, Parav Pandit wrote: > > In middle of debugging/using setup right now for other issue. > > I am basically using nvme-rdma target mode code and somewhere in path > of MR or QP setup it fails. > > I am suspecting MR because QP1 creation has passed. > > I will get to the bottom of this to provide traces tomorrow. > Sorry. I didn't any chance last whole week to debug it. > Hello Parav, > > The I/O MMU was disabled while I prepared and tested the patch series that > reworks DMA support for RDMA drivers. I assume that the error message > you reported means that the I/O MMU was enabled on your test setup? Yes. Iommu is enabled. >If so, can you check whether the patch below makes the mlx5 driver (and all > other RDMA > drivers) work again on your test setup? > I tested this patch. It works with mlx5 driver. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
