From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: Kernel and ADM hardware roulette ( was AMD graphics performance regression in 4.15 and later ) Date: Mon, 11 Jun 2018 09:15:01 +0200 Message-ID: <20180611071501.GA1015@lst.de> References: <516cddbe-73c2-01f3-a552-0d9fd75ce63a@amd.com> <8f7d00f9-992f-cc07-6bd0-b1b47c5d2ccf@amd.com> <267c42ce-91e2-4843-3815-904ac74b2f44@amd.com> <20180608060223.GB24107@lst.de> <1c8b3938-6656-5d5a-f65d-dfd2e55d989e@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Gabriel C Cc: Christian =?iso-8859-1?Q?K=F6nig?= , Christoph Hellwig , Tom Lendacky , Jean-Marc Valin , Dave Airlie , Felix Kuehling , LKML , dri-devel@lists.freedesktop.org, Joerg Roedel , alexander.deucher@amd.com, Andrew Morton , Linus Torvalds , Michel =?iso-8859-1?Q?D=E4nzer?= List-Id: dri-devel@lists.freedesktop.org I think the prime issue is that dma_direct_alloc respects the dma mask. Which we don't need if actually using the iommu. This would be mostly harmless exept for the the SEV bit high in the address that makes the checks fail. For now I'd say revert this commit for 4.17/4.18-rc and I'll look into addressing these issues properly.