[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200610071410.GD1397@lst.de>
Date: Wed, 10 Jun 2020 09:14:10 +0200
From: Christoph Hellwig <hch@....de>
To: David Rientjes <rientjes@...gle.com>
Cc: Christoph Hellwig <hch@....de>,
"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 10:26:45PM -0700, David Rientjes wrote:
> If this option should not implicitly be set for DMA_COHERENT_POOL, then I
> assume we need yet another Kconfig option since DMA_REMAP selected it
> before and DMA_COHERENT_POOL selects DMA_REMAP :)
Yes, but what do we actually need DMA_REMAP for just for the coherent
pool? We shuldn't really remap anything for AMD-SEV. Sorry for not
noticing this earlier.
Powered by blists - more mailing lists