Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp320057pxv; Thu, 8 Jul 2021 03:21:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxtZjkSza8pM100CKYn0GcQi4YpU7uJXIS4vU9eTl4egFjW06eGe3udlXfUSjf+QVViQAGF X-Received: by 2002:a02:204:: with SMTP id 4mr9401652jau.66.1625739665679; Thu, 08 Jul 2021 03:21:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625739665; cv=none; d=google.com; s=arc-20160816; b=imseR3pppMN5+E4UwOe/74U6i6TgeqscgMtsgHVyhCCm8avH0YIvg2y1Jesg8HZH5x 4mJR5eAtzXBWDdJ4q5RRqgi3yHe+ke2J2j4fELq+VU6NZ7arYdTmGFyneqdajOPeK/eG PNmrlZCTlHQ3113GNCr1h6AaUQpNSkCsurxR9IUEeqt8VLrnMzFUzFgsn9D5dSdlj61o W1FpB9w1Q/EVu/t00POTlhnNDfzggWCNbU7Yh4MAdRz07ylndFPvGCuySYEvl80mvVRb J8QkI02dXzVDjbvCz00NaFm6KQRRZzVKn2f2gz62jZDtfD2bJgCqZrqWqrbru+HBK7JH zYqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=wvyBApKhDhwDHZXh2b9S4XAMsnhmrOhL3+jrXVbBdiM=; b=0Q/XFR6p5MlCfhH2ZgFsy1zsC5JOH82B89SIx7761DXMpDPsmeucr9btEpKaaXisLT fQRbYo5V5sukx8fw1eng1jNZeO2KHWkGbjiuyOfZ8qCMNN0N39R4us1lm8DOV8eEKunG ZOwYrwjMlPOSvC1K/c5FizdEo4KtUCzDk9Fm5AdWf9Hr8eLUEAr1CdJfLrjzJ+MgSN/Z bDvGAE4T2OBwgBjL1jzC1iq+YLRjUJA9R8cVRshjITffwri4eY4lKS7HKvYFVL/dvYMv 3EFLGRukRjiSImraHuKO7xEyM1m8/Dky7A9hvYnV7oDg2NkhUX80kjX3Kjx7qzCEE827 Nm1g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a14si1999729jat.22.2021.07.08.03.20.51; Thu, 08 Jul 2021 03:21:05 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231435AbhGHKVd (ORCPT + 99 others); Thu, 8 Jul 2021 06:21:33 -0400 Received: from foss.arm.com ([217.140.110.172]:55600 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231372AbhGHKVd (ORCPT ); Thu, 8 Jul 2021 06:21:33 -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 C223CED1; Thu, 8 Jul 2021 03:18:51 -0700 (PDT) Received: from [10.57.35.192] (unknown [10.57.35.192]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E03C63F5A1; Thu, 8 Jul 2021 03:18:50 -0700 (PDT) Subject: Re: [PATCH] iommu/amd: Enable swiotlb if any device supports iommu v2 and uses identity mapping To: Joerg Roedel , Kai-Heng Feng Cc: will@kernel.org, "open list:AMD IOMMU (AMD-VI)" , open list References: <20210708074232.924844-1-kai.heng.feng@canonical.com> From: Robin Murphy Message-ID: Date: Thu, 8 Jul 2021 11:18:45 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-07-08 10:28, Joerg Roedel wrote: > On Thu, Jul 08, 2021 at 03:42:32PM +0800, Kai-Heng Feng wrote: >> @@ -344,6 +344,9 @@ static int iommu_init_device(struct device *dev) >> >> iommu = amd_iommu_rlookup_table[dev_data->devid]; >> dev_data->iommu_v2 = iommu->is_iommu_v2; >> + >> + if (dev_data->iommu_v2) >> + swiotlb = 1; > > This looks like the big hammer, as it will affect all other systems > where the AMD GPUs are in their own group. > > What is needed here is an explicit check whether a non-iommu-v2 device > is direct-mapped because it shares a group with the GPU, and only enable > swiotlb in this case. Right, it's basically about whether any DMA-limited device might at any time end up in an IOMMU_DOMAIN_IDENTITY domain. And given the possibility of device hotplug and the user being silly with the sysfs interface, I don't think we can categorically determine that at boot time. Also note that Intel systems are likely to be similarly affected (in fact intel-iommu doesn't even have the iommu_default_passthough() check so it's probably even easier to blow up). Robin.