Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756131AbdGXRQf (ORCPT ); Mon, 24 Jul 2017 13:16:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44782 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756107AbdGXRQZ (ORCPT ); Mon, 24 Jul 2017 13:16:25 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 7B1217AEBE Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=alex.williamson@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 7B1217AEBE Date: Mon, 24 Jul 2017 11:16:21 -0600 From: Alex Williamson To: Robin Murphy Cc: Will Deacon , Anup Patel , Joerg Roedel , Baptiste Reynal , Scott Branden , Linux Kernel , Linux ARM Kernel , Linux IOMMU , kvm@vger.kernel.org, BCM Kernel Feedback Subject: Re: [PATCH 3/5] iommu/arm-smmu-v3: add IOMMU_CAP_BYPASS to the ARM SMMUv3 driver Message-ID: <20170724111621.7f1c3a85@w520.home> In-Reply-To: <8e82d8f5-e5e2-dd09-c774-29f9eda2ecdd@arm.com> References: <1500456838-18405-1-git-send-email-anup.patel@broadcom.com> <1500456838-18405-4-git-send-email-anup.patel@broadcom.com> <20170719112524.GF13642@arm.com> <20170719113325.GI13642@arm.com> <20170719115333.GJ13642@arm.com> <20170720091003.GA17837@arm.com> <8e82d8f5-e5e2-dd09-c774-29f9eda2ecdd@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Mon, 24 Jul 2017 17:16:25 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2447 Lines: 50 On Thu, 20 Jul 2017 12:17:12 +0100 Robin Murphy wrote: > On 20/07/17 10:10, Will Deacon wrote: > > On Thu, Jul 20, 2017 at 09:32:00AM +0530, Anup Patel wrote: > >> On Wed, Jul 19, 2017 at 5:23 PM, Will Deacon wrote: > >>> There are two things here: > >>> > >>> 1. iommu_present() is pretty useless, because it applies to a "bus" which > >>> doesn't actually tell you what you need to know for things like the > >>> platform_bus, where some masters might be upstream of an SMMU and > >>> others might not be. > >> > >> I agree with you. The iommu_present() check in vfio_iommu_group_get() > >> is not much useful. We only reach line which checks iommu_present() > >> when iommu_group_get() returns NULL for given "struct device *". If there > >> is no IOMMU group for a "struct device *" then it means there is no IOMMU > >> HW doing translations for such device. > >> > >> If we drop the iommu_present() check (due to above reasons) in > >> vfio_iommu_group_get() then we don't require the IOMMU_CAP_BYPASS > >> and we can happily drop PATCH1, PATCH2, and PATCH3. > >> > >> I will remove the iommu_present() check in vfio_iommu_group_get() > >> because it is only comes into actions when VFIO_NOIOMMU is > >> enabled. This will also help us drop PATCH1-to-PATCH3. > > > > I don't think that's the right answer. Whilst iommu_present has obvious > > shortcomings, its intention is clear: it should tell you whether a given > > *device* is upstream of an IOMMU. So the right fix is to make this > > per-device, instead of per-bus. Removing it altogether is worse than leaving > > it like it is. > > Not really - if there is an IOMMU up and running to the point of setting > bus ops, every device it cares about can be expected to have a group > already (there are only a couple of drivers left that don't use groups, > and they're hardly relevant to VFIO). Thus iommu_group_get() already is > the de-facto per-device IOMMU check. > > And having looked into it, I'm now spinning a couple of patches to > finish off making groups truly mandatory so that that can be less > de-facto ;) No, look at vfio-noiommu and even vfio-mdev devices for devices which have an iommu group but there is no physical iommu supporting them. iommu_present() is how we can distinguish these groups and therefore not generate a segfault in trying to use the full IOMMU API on them. Thanks, Alex