[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F3529576D8E232409F431C309E29399336C5FF78@CRSMSX102.amr.corp.intel.com>
Date: Fri, 13 Jan 2017 21:08:46 +0000
From: "Estrin, Alex" <alex.estrin@...el.com>
To: Bart Van Assche <Bart.VanAssche@...disk.com>,
"dledford@...hat.com" <dledford@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: RE: [PATCH v2 00/26] IB: Optimize DMA mapping
>
> Hello Alex,
>
> Sorry for this. Can you check whether the patch below fixes this regression?
>
> diff --git a/drivers/infiniband/sw/rdmavt/vt.c
> b/drivers/infiniband/sw/rdmavt/vt.c
> index 6a81b179f631..f7fcd015ec09 100644
> --- a/drivers/infiniband/sw/rdmavt/vt.c
> +++ b/drivers/infiniband/sw/rdmavt/vt.c
> @@ -778,8 +778,7 @@ int rvt_register_device(struct rvt_dev_info *rdi)
> }
>
> /* DMA Operations */
> - if (rdi->ibdev.dma_device->dma_ops == NULL)
> - set_dma_ops(rdi->ibdev.dma_device, &dma_virt_ops);
> + set_dma_ops(rdi->ibdev.dma_device, &dma_virt_ops);
>
> /* Protection Domain */
> spin_lock_init(&rdi->n_pds_lock);
> --
> 2.11.0
>
> I will make sure that this series applies cleanly on top of v4.10-rc3 when I
> repost it.
>
> Bart.
Hi Bart,
It didn't fix the failure... Apparently there is an issue with generic mapping itself.
Thanks,
Alex.
Powered by blists - more mailing lists