From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753437AbeDKPcV (ORCPT ); Wed, 11 Apr 2018 11:32:21 -0400 Received: from foss.arm.com ([217.140.101.70]:50724 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752335AbeDKPcT (ORCPT ); Wed, 11 Apr 2018 11:32:19 -0400 Subject: Re: [PATCH V2] drm/amdgpu: limit DMA size to PAGE_SIZE for scatter-gather buffers To: Sinan Kaya , amd-gfx@lists.freedesktop.org, timur@codeaurora.org, sulrich@codeaurora.org Cc: Tom St Denis , "David (ChunMing) Zhou" , Emily Deng , David Airlie , linux-arm-msm@vger.kernel.org, Felix Kuehling , open list , "open list:DRM DRIVERS" , David Panariti , Jim Qu , Huang Rui , Roger He , Monk Liu , Feifei Xu , Alex Deucher , =?UTF-8?Q?Christian_K=c3=b6nig?= , linux-arm-kernel@lists.infradead.org, iommu@lists.linux-foundation.org, hch@lst.de References: <1523394001-4615-1-git-send-email-okaya@codeaurora.org> <32b82296-bba5-b5f1-266b-45c1ed66da94@arm.com> <1a1d0069-c8d3-cc0d-cf1c-8e90e4a2b0d7@codeaurora.org> From: Robin Murphy Message-ID: <2d812da5-1c0d-0e53-83f2-ba1781a12fe9@arm.com> Date: Wed, 11 Apr 2018 16:32:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1a1d0069-c8d3-cc0d-cf1c-8e90e4a2b0d7@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/04/18 15:33, Sinan Kaya wrote: > On 4/11/2018 8:03 AM, Robin Murphy wrote: >> On 10/04/18 21:59, Sinan Kaya wrote: >>> Code is expecing to observe the same number of buffers returned >>> from dma_map_sg() function compared to >>> sg_alloc_table_from_pages(). This doesn't hold true universally >>> especially for systems with IOMMU. >> >> So why not fix said code? It's clearly not a real hardware >> limitation, and the map_sg() APIs have potentially returned fewer >> than nents since forever, so there's really no excuse. > > Sure, I'll take a better fix if there is one. > >> >>> IOMMU driver tries to combine buffers into a single DMA address >>> as much as it can. The right thing is to tell the DMA layer how >>> much combining IOMMU can do. >> >> Disagree; this is a dodgy hack, since you'll now end up passing >> scatterlists into dma_map_sg() which already violate max_seg_size >> to begin with, and I think a conscientious DMA API implementation >> would be at rights to fail the mapping for that reason (I know >> arm64 happens not to, but that was a deliberate design decision to >> make my life easier at the time). >> >> As a short-term fix, at least do something like what i915 does and >> constrain the table allocation to the desired segment size as well, >> so things remain self-consistent. But still never claim that faking >> a hardware constraint as a workaround for a driver shortcoming is >> "the right thing to do" ;) > > You are asking for something like this from here, right? > > https://elixir.bootlin.com/linux/v4.16.1/source/drivers/gpu/drm/i915/i915_gem_dmabuf.c#L58 I just looked for callers of __sg_alloc_table_from_pages() with a limit other than SCATTERLIST_MAX_SEGMENT, and found __i915_gem_userptr_alloc_pages(), which at first glance appears to be doing something vaguely similar to amdgpu_ttm_tt_pin_userptr(). Robin.