Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp912915ybp; Thu, 17 Oct 2019 05:30:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqyb241Fr24K6TcoB/oGsoMngbPFDgNTZ4J06phi0b57B/i+gw+SWHvvE8EODdidRftFD/es X-Received: by 2002:a17:906:250d:: with SMTP id i13mr3260115ejb.275.1571315433553; Thu, 17 Oct 2019 05:30:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571315433; cv=none; d=google.com; s=arc-20160816; b=kM2Sr4xHWk9O1hBFWBrjz62+JeL6qnfgiLIBUM1Nrz0Lg5oL5xfvLfR2GgmkKoqTkb RswIdzTEO6r/9g+UY/yrGAmaITLIogzIOacOkcGZyzEzSvWlfHwelc1irNlB12wWUNws 3NJ1eW3Z6wyvsp4yFFoeMcy0xJ45Bbkaii4096wbjOYffdeqQXPwJ+IjHlgdfKzjgeSB TZFYnUGBlQjuQCu6Qyw3uXlNIQ59Jo6Lj1ofcwmtnfr76iqMmB+dTy63AL1tWmEn90KS yml9MVodM1kAmkR98gAPduS29z46J3zbaomAX/+QewuNuV25sG46zVjIuEPIC8EZxMMm NeBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=V9jBa9Q3WO6rRDXrf0AAaGGN+PYHeZpdebjlLrFoKDg=; b=jEIYoU5XsERsA3vpISkey5zXqcXC2x5uBUYw9UGwnMfV+6+VfXGnIdUFWgLyK0mOOD 5mbGSeuGL+1CqyCKrM7G0f3qzlSIdg+0iYgP5P7GBISCbT5jdMaaf+X15LYE2OxbFdD9 Wps1h/ceeLdDei4V3ozZ4LwlSV5zLR8vTe9rZ/M6+hcs+rQV1ocyfhp0EL/25dvKAb+Y 7mOdZKwXwUnW8FH8TeIxQq/c9y8e8sGdidCQEWuCxDwaJK8W/7jNmSl7iZp6MLjR3ZAD nbZy+XyewN9D37BYx2d7soWiPjbbr6qnypqcxNlQI2PEsAfl85DxznwTczLPYYBzConq leng== 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 b47si1487153edc.45.2019.10.17.05.30.10; Thu, 17 Oct 2019 05:30:33 -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 S2406344AbfJPQgO (ORCPT + 99 others); Wed, 16 Oct 2019 12:36:14 -0400 Received: from foss.arm.com ([217.140.110.172]:45190 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404745AbfJPQgO (ORCPT ); Wed, 16 Oct 2019 12:36:14 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A93C628; Wed, 16 Oct 2019 09:36:13 -0700 (PDT) Received: from [10.1.196.50] (e108454-lin.cambridge.arm.com [10.1.196.50]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 80C143F68E; Wed, 16 Oct 2019 09:36:12 -0700 (PDT) Subject: Re: "Convert the AMD iommu driver to the dma-iommu api" is buggy To: Robin Murphy , Joerg Roedel , Qian Cai Cc: iommu@lists.linux-foundation.org, Christoph Hellwig , Tom Murphy , linux-kernel@vger.kernel.org, Marc Zyngier References: <1571237707.5937.58.camel@lca.pw> <1571237982.5937.60.camel@lca.pw> <20191016153112.GF4695@suse.de> <1571241213.5937.64.camel@lca.pw> <20191016160314.GH4695@suse.de> From: Julien Grall Message-ID: Date: Wed, 16 Oct 2019 17:36:11 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Robin, On 16/10/2019 17:09, Robin Murphy wrote: > On 16/10/2019 17:03, Joerg Roedel wrote: >> On Wed, Oct 16, 2019 at 11:53:33AM -0400, Qian Cai wrote: >>> On Wed, 2019-10-16 at 17:31 +0200, Joerg Roedel wrote: >> >>> The x86 one might just be a mistake. >>> >>> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c >>> index ad05484d0c80..63c4b894751d 100644 >>> --- a/drivers/iommu/amd_iommu.c >>> +++ b/drivers/iommu/amd_iommu.c >>> @@ -2542,7 +2542,7 @@ static int amd_iommu_map(struct iommu_domain *dom, >>> unsigned long iova, >>>          if (iommu_prot & IOMMU_WRITE) >>>                  prot |= IOMMU_PROT_IW; >>> -       ret = iommu_map_page(domain, iova, paddr, page_size, prot, GFP_KERNEL); >>> +       ret = iommu_map_page(domain, iova, paddr, page_size, prot, gfp); >> >> Yeah, that is a bug, I spotted that too. >> >>> @@ -1185,7 +1185,7 @@ static struct iommu_dma_msi_page >>> *iommu_dma_get_msi_page(struct device *dev, >>>          if (!iova) >>>                  goto out_free_page; >>> -       if (iommu_map(domain, iova, msi_addr, size, prot)) >>> +       if (iommu_map_atomic(domain, iova, msi_addr, size, prot)) >>>                  goto out_free_iova; >> >> Not so sure this is a bug, this code is only about setting up MSIs on >> ARM. It probably doesn't need to be atomic. > Right, since the iommu_dma_prepare_msi() operation was broken out to happen at > MSI domain setup time, I don't think the comment in there applies any more, so > we can probably stop disabling irqs around the iommu_dma_get_msi_page() call. Yes, I agree that it does not need to be atomic anymore. Cheers, -- Julien Grall