[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1525969846.5308.2.camel@gmx.de>
Date: Thu, 10 May 2018 18:30:46 +0200
From: Mike Galbraith <efault@....de>
To: Jerome Glisse <jglisse@...hat.com>
Cc: nouveau <nouveau@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
Ben Skeggs <bskeggs@...hat.com>
Subject: Re: [Nouveau] kernel spew from nouveau/ swiotlb
On Thu, 2018-05-10 at 17:31 +0200, Mike Galbraith wrote:
> On Thu, 2018-05-10 at 10:31 -0400, Jerome Glisse wrote:
> >
> > Could you bisect ? I would love to point finger upstream to the DMA
> > folk who made changes to that API without testing with GPU.
>
> Rummaging a bit, it might be...
>
(unsend, whack duplicate line, munge, send;)
> nouveau_bo_new()
> ...
> ttm_dma_pool_alloc_new_pages()
> dma_alloc_attrs()
> ops->alloc() == x86_swiotlb_alloc_coherent()
> x86_swiotlb_alloc_coherent() flags |= __GFP_NOWARN;
> swiotlb_alloc_coherent(..flags)
> swiotlb_alloc_coherent(..flags) attrs = (flags & __GFP_NOWARN) ? DMA_ATTR_NO_WARN : 0;
> swiotlb_alloc_buffer(..attrs)
* swiotlb_tbl_map_single(..0) passed 0 vs attrs, gripeage follows
Or something like that.
Powered by blists - more mailing lists