On Tue, Feb 09, 2021 at 12:45:11PM +, Robin Murphy wrote:
> It's not a bug, it's a fundamental design failure. dma_get_sgtable() has
> only ever sort-of-worked for DMA buffers that come from CMA or regular page
> allocations. In particular, a "no-map" DMA pool is not backed by kernel
> memor
On 2021-02-09 12:36, Sumit Garg wrote:
Hi Christoph,
On Tue, 9 Feb 2021 at 15:06, Christoph Hellwig wrote:
On Tue, Feb 09, 2021 at 10:23:12AM +0100, Greg KH wrote:
From the view point of ZeroCopy using DMABUF, is 5.4 not
mature enough, and is 5.10 enough mature ?
This is the most impor
Hi Christoph,
On Tue, 9 Feb 2021 at 15:06, Christoph Hellwig wrote:
>
> On Tue, Feb 09, 2021 at 10:23:12AM +0100, Greg KH wrote:
> > > From the view point of ZeroCopy using DMABUF, is 5.4 not
> > > mature enough, and is 5.10 enough mature ?
> > > This is the most important point for judging m
On Tue, Feb 09, 2021 at 10:19:07AM +, obayashi.yoshim...@socionext.com
wrote:
> > How do you judge "mature"?
>
> My basic criteria are
> * Function is exist, but bug fix is necessary: "mature"
> * Function extension is necessary: "immature"
>
> > And again, if a feature isn't present in a
; To: Obayashi, Yoshimasa/尾林 善正
> Cc: sumit.g...@linaro.org; h...@lst.de; m.szyprow...@samsung.com;
> robin.mur...@arm.com;
> io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
> sta...@vger.kernel.org;
> daniel.thomp...@linaro.org
> Subject: Re: DMA direct mapping
On Tue, Feb 09, 2021 at 10:23:12AM +0100, Greg KH wrote:
> > From the view point of ZeroCopy using DMABUF, is 5.4 not
> > mature enough, and is 5.10 enough mature ?
> > This is the most important point for judging migration.
>
> How do you judge "mature"?
>
> And again, if a feature isn't pr
On Tue, Feb 09, 2021 at 09:05:40AM +, obayashi.yoshim...@socionext.com
wrote:
> > > As the drivers are currently under development and Socionext has
> > > chosen 5.4 stable kernel for their development. So I will let
> > > Obayashi-san answer this if it's possible for them to migrate to 5.10
>
y, February 9, 2021 5:04 PM
> To: Sumit Garg
> Cc: Obayashi, Yoshimasa/尾林 善正 ; h...@lst.de;
> m.szyprow...@samsung.com; robin.mur...@arm.com;
> io...@lists.linux-foundation.org; Linux Kernel Mailing
> List ; stable ; Daniel
> Thompson
>
> Subject: Re: DMA direct mapping fix fo
On Tue, Feb 09, 2021 at 01:28:47PM +0530, Sumit Garg wrote:
> Thanks Greg for your response.
>
> On Tue, 9 Feb 2021 at 12:28, Greg Kroah-Hartman
> wrote:
> >
> > On Tue, Feb 09, 2021 at 11:39:25AM +0530, Sumit Garg wrote:
> > > Hi Christoph, Greg,
> > >
> > > Currently we are observing an incorre
Thanks Greg for your response.
On Tue, 9 Feb 2021 at 12:28, Greg Kroah-Hartman
wrote:
>
> On Tue, Feb 09, 2021 at 11:39:25AM +0530, Sumit Garg wrote:
> > Hi Christoph, Greg,
> >
> > Currently we are observing an incorrect address translation
> > corresponding to DMA direct mapping methods on 5.4
On Tue, Feb 09, 2021 at 11:39:25AM +0530, Sumit Garg wrote:
> Hi Christoph, Greg,
>
> Currently we are observing an incorrect address translation
> corresponding to DMA direct mapping methods on 5.4 stable kernel while
> sharing dmabuf from one device to another where both devices have
> their own
Hi Christoph, Greg,
Currently we are observing an incorrect address translation
corresponding to DMA direct mapping methods on 5.4 stable kernel while
sharing dmabuf from one device to another where both devices have
their own coherent DMA memory pools.
I am able to root cause this issue which is
12 matches
Mail list logo
