Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2944165pxk; Mon, 28 Sep 2020 04:36:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzaM8W1UXce+Loot4LB7bWPvw688smTHHMMlApq+JIkmiIDcg1Panme6/qzvGj8afkAqzvZ X-Received: by 2002:aa7:df14:: with SMTP id c20mr1217510edy.334.1601292967181; Mon, 28 Sep 2020 04:36:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601292967; cv=none; d=google.com; s=arc-20160816; b=CXhpxQU5/7gSw98NRAT67n7bbyKS2N9uTHfyQTXml6y7I7lEzXtdIs0kRAkktoUoYA NjRml8pfGDsdJYBFK6nUaoWbkjTCWYQma8sT6pLxp9v7onB4EVqIcQ8Ij9AwTXaqvs4F kgWMNYIQegKC8Aq0UNoNB3KFATFDhFbGGUEDjD/zdEwyIQSNDKqJHlfT55ot5tsQ3RJA jiwAT2/0x4evaeBcMn5vd9o5jdw7iXEE7Xwlgsr7uKockbLuC04mWaCtvk2trKydBoXq T/rjl0h64E1owIwFUnLWUxZSfmrrFlqB7sQQSE7Rm8h7G7HUNP8ZLTeCeZ8JGlbn/C+q O5tA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tFfb2y3Fj4MEijILL8/3ihaaD3ujMlfXbdIUIdpcV54=; b=FwW0czyHy1seR+sl12z1Z4U79ddkNXAGTc+/gzTYbCtTypGp0oho0IVLFC92WJOOZS D5FZFolo+cgyQYagdJ/VP4hRzwrU1PFkNiMboIaYAGF8lv0r28AWGLxoT6EszQsYU3dD X0F7lsXTkPUFzJfsMyn4OZqrnTMQHn6GEFHvewgVSiNIZYAT4tsLLHF9Tkaffu3NfNQE qDHmmJ3sCDkA33Xc5+trTAFxjWdItPFTCWcF0S5QkDpcit76eDm7Te0EGkEsfu1bq/ny teQZ8BP1e8SVIgHKB8jJHFk+YoN0uVcIEAv6KiO/E3eyfPFnE2oFu81wNOPsEM0XbWRJ GG7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rv15si412048ejb.364.2020.09.28.04.35.44; Mon, 28 Sep 2020 04:36:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726801AbgI1LeU (ORCPT + 99 others); Mon, 28 Sep 2020 07:34:20 -0400 Received: from verein.lst.de ([213.95.11.211]:35259 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726793AbgI1LeT (ORCPT ); Mon, 28 Sep 2020 07:34:19 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 5178268AFE; Mon, 28 Sep 2020 13:34:16 +0200 (CEST) Date: Mon, 28 Sep 2020 13:34:15 +0200 From: Christoph Hellwig To: Paul Cercueil Cc: Christoph Hellwig , Stephen Rothwell , Dave Airlie , DRI , Linux Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build failure after merge of the drm tree Message-ID: <20200928113415.GA555@lst.de> References: <20200928135405.73404219@canb.auug.org.au> <20200928060427.GA15041@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 28, 2020 at 12:15:56PM +0200, Paul Cercueil wrote: > Hi Christoph, > > Le lun. 28 sept. 2020 ? 8:04, Christoph Hellwig a ?crit : >> On Mon, Sep 28, 2020 at 01:54:05PM +1000, Stephen Rothwell wrote: >>> Hi all, >>> >>> After merging the drm tree, today's linux-next build (x86_64 >>> allmodconfig) >>> failed like this: >> >> The driver needs to switch do dma_alloc_noncoherent + dma_sync_single* >> like the other drivers converted in the dma tree. Paul, let me know if >> you have any questions. > > I don't dma_alloc* anything, DRM core does. I use the > DMA_ATTR_NON_CONSISTENT attr with dma_mmap_attrs(). Is there a replacement > for that? dma_mmap_attrs can only be used on allocations from dma_mmap_attrs with the same attrs. As there is no allocation using DMA_ATTR_NON_CONSISTENT in the drm core, something looks very fishy here. Where does the allocation you try to mmap come from? All the allocations in drivers/gpu/drm/drm_gem_cma_helper.c seems to use dma_alloc_wc (aka dma_allloc_attrs with the DMA_ATTR_WRITE_COMBINE flag).