Received: by 10.213.65.68 with SMTP id h4csp1710107imn; Mon, 19 Mar 2018 11:07:51 -0700 (PDT) X-Google-Smtp-Source: AG47ELuthN7SBk29ylbl7VgoA6bi0dYgk2E2H+UgcZoTgkzhAFniVPifxYtwejRRVYoIesONwmzn X-Received: by 2002:a17:902:9045:: with SMTP id w5-v6mr13753814plz.104.1521482871044; Mon, 19 Mar 2018 11:07:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521482870; cv=none; d=google.com; s=arc-20160816; b=IDe2WetZyo6TkyKOH0M84hwZRxTbraYVeGtdbIB44Rt4I5Ijp3jBWswsPzFhuMjnlY rIokcMELKHP12lMPUBGtryjSELNDtMb9BoG5Wd6eDMTy9yEqPS5YLuAE9aC6buaJ/C60 AYK0lKvtiCJfb5AkivUyB/OHJgZRO2eT2n2++tC0sKcVVNgXSRpk/ePpJkkwaMMwovXh KjTQENH0tQtGlF8wzsB9udXPuYz+21uD7aX8Rg8oC5mLQVWxHa1L2xXJIf05q2xsyNAC 0PxebvZO7LuiTAgJcHpXhdH0QD9aLIB3nHVlKx+osGO4Qq/QgefbIy6J+m1vcZdvOGhp cFYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=LJ1GWTYj6UTlk75L0LMA8szr+8YJnzLZdKZ2798xFps=; b=O3sKSXPtG3eXFsxUKmEw4Q4nbSJ18FYhJrDXjlFLeWsXXMIwZcZ0nx3djRa9uVHqc2 +S5I2yDnfNrij7EpmKngSdILjrMdHzzkTbcD6jS5JAJMDyrTmXN/+BA149O2mH/5Ktha kngPSrIC94O3e7yuLoOap2IP0V1alpvJ+F5rW+syFibzfEkE+aj1ZUJyKEPH0iC3YxkW cDOH7eswGHfG7cTk/TN2OXBzNczrR+xgU6+MI6DfMIu3fPzcrm66oHUi3++SMal7L3nw CQOHzHAuuMvKW5mpBM51/TfYKaXtX0H5VlwGHzoTz2yymLOs/6FLNlSBgPuE2GJgunFy WL6w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y2-v6si381347plh.649.2018.03.19.11.07.36; Mon, 19 Mar 2018 11:07:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030413AbeCSSGG (ORCPT + 99 others); Mon, 19 Mar 2018 14:06:06 -0400 Received: from verein.lst.de ([213.95.11.211]:59574 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965570AbeCSQDp (ORCPT ); Mon, 19 Mar 2018 12:03:45 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id BA3A17FDDF; Mon, 19 Mar 2018 17:03:43 +0100 (CET) Date: Mon, 19 Mar 2018 17:03:43 +0100 From: Christoph Hellwig To: Will Deacon Cc: Robin Murphy , Christoph Hellwig , x86@kernel.org, Tom Lendacky , Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org, Muli Ben-Yehuda , iommu@lists.linux-foundation.org, David Woodhouse , Catalin Marinas Subject: Re: [PATCH 12/14] dma-direct: handle the memory encryption bit in common code Message-ID: <20180319160343.GA29002@lst.de> References: <20180319103826.12853-1-hch@lst.de> <20180319103826.12853-13-hch@lst.de> <20180319152442.GA27915@lst.de> <5316b479-7e75-d62f-6b17-b6bece55187c@arm.com> <20180319154832.GD14916@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180319154832.GD14916@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 19, 2018 at 03:48:33PM +0000, Will Deacon wrote: > Why can't we just resolve the conflict by adding the underscores? We can solve the conflict easily that way. But that's not the point. The point is that I've been fighting hard to consolidate dma code given that the behavior really is common and not arch specific. And this one is another case like that: the fact that the non-coherent dma boundary is bigger than the exposed size is something that can easily happen elsewhere, so there is no need to duplicate a lot of code for that. Nevermind that the commit should at least be three different patches: (1) revert the broken original commit (2) increase the dma min alignment (3) put the swiotlb workaround in place