Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4856022ybl; Sat, 21 Dec 2019 15:47:30 -0800 (PST) X-Google-Smtp-Source: APXvYqyRtjcC7LHk0iI0Rwth46+34dzcJ2w2FGiZA5KXIqtNLxTGJDNYj4JpROClts83P596IKC1 X-Received: by 2002:a9d:4c94:: with SMTP id m20mr18995520otf.341.1576972050180; Sat, 21 Dec 2019 15:47:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576972050; cv=none; d=google.com; s=arc-20160816; b=R1PE1bicw4ckRuSFx3DY8+nC9uXGCm36ciZqCRitg0o7Vo7PQBf9NZhG49Z4iV+Uqa 88CSYO3Z7oA78gviUCZrmTRzP1GpREKejRpT2mhd5k8g/j+3TYHKd/MxrG2Vg+lMkEAR G0R8hO6DzvDVM3RcTidj91Jn6iSxkNL9twifBBgcpD9Rsb7zGp9kAMNqjGN/thSjOrLC +OfFSupsMyNcfvePWA64LXjF+S0lPCp7Gs3/smBXRDDb60fXZD8Guw6hMdHKYeG+jdfe 4YwMHgz57KesTEwFFPMVp2m3qCY1L62X9/kzSNCXpJdONY2qaKu/ZuepaZ//u9RdrOHp W1eg== 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:date:from:dkim-signature; bh=DZy1sByRbPp81Fc4unsIfUDkM1speXohHbJEFLa+79Y=; b=PHK1gNh2B1z/5lzlEDjKyrfbxXpQRemDFKiHF5x/21s2tyrmlE2V9CZoiMc2OkrvmX GHqtNTCJ3WdH01NnnHybjnxe03wdrUJKL01Qzb1PJnkMV7lBkI6SZEHwhGxU6upXJkPr r/xEYF/thP4sD6Tf768AoxwZ3VrqtiFsgL0Li8H/sspZ+2KxAdwWR5RCpOou4uSc23GZ PeS2sp6d+Gj/+7E8k9MF6GeLv1QBJScp8HG3L/+J1WxY+RpT55Cn2AUCfjk0gly5SHQW w0DtPZYurgW71YobeWdhMZWECnuAfuRJ0xaIylocO1zWTBrRwWlantlXhS8ohwIZWrb0 T4sQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=K2F08+kb; 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 e1si1069614otj.276.2019.12.21.15.47.18; Sat, 21 Dec 2019 15:47:30 -0800 (PST) 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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=K2F08+kb; 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 S1726787AbfLUXqm (ORCPT + 99 others); Sat, 21 Dec 2019 18:46:42 -0500 Received: from mail-qv1-f65.google.com ([209.85.219.65]:34193 "EHLO mail-qv1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726024AbfLUXqm (ORCPT ); Sat, 21 Dec 2019 18:46:42 -0500 Received: by mail-qv1-f65.google.com with SMTP id o18so5079840qvf.1; Sat, 21 Dec 2019 15:46:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DZy1sByRbPp81Fc4unsIfUDkM1speXohHbJEFLa+79Y=; b=K2F08+kbBOHpEb5GI2snEkwsgZNjaPXWMKDftdpnSDrNjdoFsaU7mJy1E8X+UN6pTF CqMGQGTCVzkASTJTbCKGzwmcE+xGW9X9DoBShnHYBHrUjwA2y0thgfSaIDeXsAsxh80K Lzsw/9ErY21ZUOic82HoE2snRWWJy1wLWDPwW7IWmh5yvrdgv4rUVX4xVE004OheL+PI /8AUmTvOKwGIU5Ku/sIm9m5U0rOim/SPjYy3gzVxef0QWGwTj1JJt9SDEH83TWoChVOq wLkEyhYrjgWcWjYym7iQAuL3qcxgGsX3JQNmgv7pU5p9IHVMooy6My1cg5SbonFnCmxX Fqwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:date:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=DZy1sByRbPp81Fc4unsIfUDkM1speXohHbJEFLa+79Y=; b=cvV8272CjqKNjseP9IVVUXbbxKJ0slLx1WsbkDJHDoeN/3vHwuctTz95T3x5v8qef4 wfQuL7StZwZjPkgUDbtB+lwe/oMAwB9Xbdy10mk/u+2jQR3GNEe7D0D74q70kMq9arlb PNhpmuqIUw/xbiPYSNl5/rUdu6ZFvqxccOvNBRozsvoS6a54JRTc/3sqU3aSAA/0JUGC Y3VAraup61c7CsK8ZBh2M96ClkM7ofpaMh+1a0fD0joJM0iWn/CYvcAr53OIWtdMFcZl FXh0enaSlbVfnKVaYH03LCc6yFScN4tbWLcZmnZySjUxro6ycPDJmnN/BrhaN27W9cjt IMDw== X-Gm-Message-State: APjAAAXdYKo5LbSIyB+ksyGRkl7Fcg1OvKReFWcuR7hCwWAQBk3DWZYm wG6m4ecW0EFirlb5YPryXQA= X-Received: by 2002:a05:6214:14b3:: with SMTP id bo19mr18216129qvb.93.1576972000657; Sat, 21 Dec 2019 15:46:40 -0800 (PST) Received: from rani.riverdale.lan ([2001:470:1f07:5f3::b55f]) by smtp.gmail.com with ESMTPSA id b7sm4323472qkh.106.2019.12.21.15.46.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Dec 2019 15:46:40 -0800 (PST) From: Arvind Sankar X-Google-Original-From: Arvind Sankar Date: Sat, 21 Dec 2019 18:46:37 -0500 To: Tom Murphy Cc: iommu@lists.linux-foundation.org, Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , Daniel Vetter , Joerg Roedel , Will Deacon , Robin Murphy , Marek Szyprowski , Kukjin Kim , Krzysztof Kozlowski , David Woodhouse , Lu Baolu , Andy Gross , Bjorn Andersson , Matthias Brugger , Rob Clark , Heiko Stuebner , Gerald Schaefer , Thierry Reding , Jonathan Hunter , Jean-Philippe Brucker , Alex Williamson , Cornelia Huck , Eric Auger , Julien Grall , Marc Zyngier , Thomas Gleixner , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-s390@vger.kernel.org, linux-tegra@vger.kernel.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org Subject: Re: [PATCH 1/8] iommu/vt-d: clean up 32bit si_domain assignment Message-ID: <20191221234635.GA99623@rani.riverdale.lan> References: <20191221150402.13868-1-murphyt7@tcd.ie> <20191221150402.13868-2-murphyt7@tcd.ie> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20191221150402.13868-2-murphyt7@tcd.ie> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 21, 2019 at 03:03:53PM +0000, Tom Murphy wrote: > In the intel iommu driver devices which only support 32bit DMA can't be > direct mapped. The implementation of this is weird. Currently we assign > it a direct mapped domain and then remove the domain later and replace > it with a domain of type IOMMU_DOMAIN_IDENTITY. We should just assign it > a domain of type IOMMU_DOMAIN_IDENTITY from the begging rather than > needlessly swapping domains. > > Signed-off-by: Tom Murphy > --- > drivers/iommu/intel-iommu.c | 88 +++++++++++++------------------------ > 1 file changed, 31 insertions(+), 57 deletions(-) > > diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c > index 0c8d81f56a30..c1ea66467918 100644 > --- a/drivers/iommu/intel-iommu.c > +++ b/drivers/iommu/intel-iommu.c > @@ -5640,7 +5609,12 @@ static int intel_iommu_add_device(struct device *dev) > domain = iommu_get_domain_for_dev(dev); > dmar_domain = to_dmar_domain(domain); > if (domain->type == IOMMU_DOMAIN_DMA) { > - if (device_def_domain_type(dev) == IOMMU_DOMAIN_IDENTITY) { > + /* > + * We check dma_mask >= dma_get_required_mask(dev) because > + * 32 bit DMA falls back to non-identity mapping. > + */ > + if (device_def_domain_type(dev) == IOMMU_DOMAIN_IDENTITY && > + dma_mask >= dma_get_required_mask(dev)) { > ret = iommu_request_dm_for_dev(dev); > if (ret) { > dmar_remove_one_dev_info(dev); > -- > 2.20.1 > Should this be dma_direct_get_required_mask? dma_get_required_mask may return DMA_BIT_MASK(32) -- it callbacks into intel_get_required_mask, but I'm not sure what iommu_no_mapping(dev) will do at this point?