[lkml]   [2021]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: DMA direct mapping fix for 5.4 and earlier stable branches
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 migration.
> >
> > How do you judge "mature"?
> >
> > And again, if a feature isn't present in a specific kernel version, why
> > would you think that it would be a viable solution for you to use?
> I'm pretty sure dma_get_sgtable has been around much longer and was
> supposed to work, but only really did work properly for arm32, and
> for platforms with coherent DMA. I bet he is using non-coherent arm64,

It's an arm64 platform using coherent DMA where device coherent DMA
memory pool is defined in the DT as follows:

reserved-memory {
#address-cells = <2>;
#size-cells = <2>;

encbuffer: encbuffer@0xb0000000 {
compatible = "shared-dma-pool";
reg = <0 0xb0000000 0 0x08000000>; // this
area used with dma-coherent

Device is dma-coherent as per following DT property:

codec {
compatible = "socionext,uniphier-pxs3-codec";
memory-region = <&encbuffer>;

And call chain to create device coherent DMA pool is as follows:


which simply maps coherent DMA memory into vmalloc space on arm64.

The thing I am unclear is why this is called a new feature rather than
a bug in dma_common_get_sgtable() which is failing to handle vmalloc
addresses? While at the same time DMA debug APIs specifically handle
vmalloc addresses [1].



> and it would be broken for other drivers there as well if people did
> test them, which they apparently so far did not.

 \ /
  Last update: 2021-02-09 13:39    [W:0.070 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site