From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0289BC432C3 for ; Thu, 14 Nov 2019 05:17:18 +0000 (UTC) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DD4D120659 for ; Thu, 14 Nov 2019 05:17:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DD4D120659 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id 7ED77AD0; Thu, 14 Nov 2019 05:17:17 +0000 (UTC) Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AA90AAC7 for ; Thu, 14 Nov 2019 05:17:15 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B81534C3 for ; Thu, 14 Nov 2019 05:17:13 +0000 (UTC) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Nov 2019 21:17:12 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,302,1569308400"; d="scan'208";a="229995322" Received: from allen-box.sh.intel.com (HELO [10.239.159.136]) ([10.239.159.136]) by fmsmga004.fm.intel.com with ESMTP; 13 Nov 2019 21:17:08 -0800 Subject: Re: [PATCH v5 02/10] iommu/vt-d: Use per-device dma_ops To: Christoph Hellwig References: <20190725031717.32317-1-baolu.lu@linux.intel.com> <20190725031717.32317-3-baolu.lu@linux.intel.com> <20190725054413.GC24527@lst.de> <20190725114348.GA30957@lst.de> <20191112071640.GA3343@lst.de> <0885617e-8390-6d18-987f-40d49f9f563e@linux.intel.com> <20191113070312.GA2735@lst.de> <20191113095353.GA5937@lst.de> From: Lu Baolu Message-ID: <0ddc8aff-783a-97b9-f5cc-9e27990de278@linux.intel.com> Date: Thu, 14 Nov 2019 13:14:11 +0800 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: <20191113095353.GA5937@lst.de> Content-Language: en-US Cc: alan.cox@intel.com, Stefano Stabellini , ashok.raj@intel.com, Jonathan Corbet , pengfei.xu@intel.com, Ingo Molnar , David Woodhouse , kevin.tian@intel.com, Konrad Rzeszutek Wilk , Steven Rostedt , Bjorn Helgaas , Boris Ostrovsky , mika.westerberg@linux.intel.com, Juergen Gross , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, jacob.jun.pan@intel.com, Robin Murphy X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: iommu-bounces@lists.linux-foundation.org Errors-To: iommu-bounces@lists.linux-foundation.org Hi Christoph, On 11/13/19 5:53 PM, Christoph Hellwig wrote: > On Wed, Nov 13, 2019 at 08:03:12AM +0100, Christoph Hellwig wrote: >> Indeed. And one idea would be to lift the code in the powerpc >> dma_iommu_ops that check a flag and use the direct ops to the generic >> dma code and a flag in struct device. We can then switch the intel >> iommu ops (and AMD Gart) over to it. > > Let me know what you think of the branch below. Only compile tested > and booted on qemu with an emulated intel iommu: > > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-bypass > I took a quick look at the related patches on the branch. Most of them look good to me. But I would like to understand more about below logic. static int intel_dma_supported(struct device *dev, u64 mask) { struct device_domain_info *info = dev->archdata.iommu; int ret; ret = dma_direct_supported(dev, mask); if (ret < 0) return ret; if (!info || info == DUMMY_DEVICE_DOMAIN_INFO || info == DEFER_DEVICE_DOMAIN_INFO) { dev->dma_ops_bypass = true; } else if (info->domain == si_domain) { if (mask < dma_direct_get_required_mask(dev)) { dev->dma_ops_bypass = false; intel_iommu_set_dma_domain(dev); dev_info(dev, "32bit DMA uses non-identity mapping\n"); } else { dev->dma_ops_bypass = true; } } else { dev->dma_ops_bypass = false; } return 0; } Could you please educate me what dma_supported() is exactly for? Will it always get called during boot? When will it be called? In above implementation, why do we need to check dma_direct_supported() at the beginning? And why if (!info || info == DUMMY_DEVICE_DOMAIN_INFO || info == DEFER_DEVICE_DOMAIN_INFO) { dev->dma_ops_bypass = true; Best regards, baolu _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu