[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200609114059.GA1228@lst.de>
Date: Tue, 9 Jun 2020 13:40:59 +0200
From: Christoph Hellwig <hch@....de>
To: Takashi Iwai <tiwai@...e.de>
Cc: Christoph Hellwig <hch@....de>,
David Rientjes <rientjes@...gle.com>,
"Alex Xu (Hello71)" <alex_y_xu@...oo.ca>,
alsa-devel@...a-project.org, bp@...en8.de, hch@...radead.org,
hpa@...or.com, linux-kernel@...r.kernel.org, mingo@...hat.com,
Pavel Machek <pavel@....cz>, perex@...ex.cz,
tglx@...utronix.de, tiwai@...e.com, x86@...nel.org
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
On Tue, Jun 09, 2020 at 01:38:46PM +0200, Takashi Iwai wrote:
> On Tue, 09 Jun 2020 13:31:23 +0200,
> Christoph Hellwig wrote:
> >
> > On Tue, Jun 09, 2020 at 11:31:20AM +0200, Takashi Iwai wrote:
> > > > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > > > with coherent memory? (Also allowing user-space mmap, too)
> > > >
> > > > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > > > have a good way for kernel space mappings.
> > >
> > > And that's the missing piece right now... :-<
> >
> > Can you point me to the relevant places (allocation and vmap mostly)
> > so that I can take a look at how to fix this mess?
>
> Found in sound/core/sgbuf.c. It's specific to x86.
So it looks like we could just turn off CONFIG_SND_DMA_SGBUF and
be done with it? After all this works on other architectures
just fine..
Powered by blists - more mailing lists