Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp594359imm; Fri, 27 Jul 2018 02:39:03 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdo7zheMgywkrPwpNOsiBVocWYyVOvIGMaWnjztGFKTr19pGFLg0JQL9I9oP9CDf+dvUzUc X-Received: by 2002:a63:b40e:: with SMTP id s14-v6mr5456383pgf.9.1532684343102; Fri, 27 Jul 2018 02:39:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532684343; cv=none; d=google.com; s=arc-20160816; b=krKfwSCBaGJVU+z5/QSoPHfPJfPsxVnXJpogptmHrN2UEuUx3qDgUHOErSnb/w6xic W08ooLdMxdXe3M372yprgR2N0MiNYul/kufbrF3dk3GVNp9c6Ihdh7aeSAKxZhRxCpwb 5GUvLklxZ/shNZIEsJJDJepCdzC1wsZiNie7ffEyGi0QL5BnFTOF0TxCOFQ7/k2OJLg1 0+0JA0wi0ldtACLobSSBu5mX9A4wikFv3ftDF+Pcv56GA/Eq4xbkl4NkYeQEuYu5/Cx0 6z4+JGnlf/hu8NNEDN91UDZDlNkx+kZzNe0Fhbk7jj5get2v4pINfOpemoZ8J/GZ/dJS k7cA== 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:from:date:arc-authentication-results; bh=ktKCaFsiBqvE05SJTKFlYsyBpgj7GLEtRvltvsgpoaY=; b=Qfn6ChOhbRMrcTWLUsPeSEvBoJprnTUbUmWi50CwU8nP+4+k+CqysjaKFMVtr8Pl1t r3LTNBydugBgpTg/IOt9an21DeeJ4h7ROQKxWQD1cUpK/jU2pJcus9VODFe57EqHPvPY T8uogXfOf4XkHE9t3pk1/QDwdOx30klz3jlEi7BSHVpf1M9JasGx1jY0Ud0tVKSFaAs8 C/ZtkgSsHSZHTce/b8UXIDd1e7OKiMdTY8jgfYsJsvRvXT8d5xx+isXMOU3xhUVqDh3i JMWzYT27Gok0jA0ty1qRVOmWHg1/jFIBIlN+0tx504K61PEzsMPz9SnM40jpZCTQdlF2 HHVw== 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 d4-v6si3266887pla.81.2018.07.27.02.38.47; Fri, 27 Jul 2018 02:39:03 -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 S1730376AbeG0K7B (ORCPT + 99 others); Fri, 27 Jul 2018 06:59:01 -0400 Received: from foss.arm.com ([217.140.101.70]:39664 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729431AbeG0K7B (ORCPT ); Fri, 27 Jul 2018 06:59:01 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5093715A2; Fri, 27 Jul 2018 02:37:58 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 1E7153F575; Fri, 27 Jul 2018 02:37:58 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id 95D741AE17A0; Fri, 27 Jul 2018 10:37:58 +0100 (BST) Date: Fri, 27 Jul 2018 10:37:58 +0100 From: Will Deacon To: "Leizhen (ThunderTown)" Cc: Robin Murphy , Jean-Philippe Brucker , Joerg Roedel , linux-arm-kernel , iommu , linux-kernel , LinuxArm Subject: Re: [PATCH v3 0/6] add non-strict mode support for arm-smmu-v3 Message-ID: <20180727093758.GL28088@arm.com> References: <1531376312-2192-1-git-send-email-thunder.leizhen@huawei.com> <5B594399.1080404@huawei.com> <5B5A8857.9040907@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5B5A8857.9040907@huawei.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 27, 2018 at 10:49:59AM +0800, Leizhen (ThunderTown) wrote: > On 2018/7/26 22:16, Robin Murphy wrote: > > On 2018-07-26 4:44 AM, Leizhen (ThunderTown) wrote: > >> Passthrough is not enough to support VFIO, and virtualization need > >> the later. > > > > Huh? The whole point of passthrough mode is that the IOMMU can still be > > used for VFIO, but without imposing the overhead of dynamic mapping on > > host DMA. > > I said that from my experience. Userspace do not known the PA, so I think > the user can not fill dma_map.iova correctly. > > /* Allocate some space and setup a DMA mapping */ > dma_map.vaddr = (__u64)mmap(0, 0x1000, PROT_READ | PROT_WRITE, > MAP_PRIVATE | MAP_ANONYMOUS, 0, 0); > dma_map.size = 0x1000; > dma_map.iova = 0x2f00000000UL; /* user specified */ > dma_map.flags = VFIO_DMA_MAP_FLAG_READ | VFIO_DMA_MAP_FLAG_WRITE; > > ioctl(container, VFIO_IOMMU_MAP_DMA, &dma_map); Hmm, I'm pretty sure that's not the case. When passthrough is configured via iommu.passthrough, it only applies to the default domain and therefore won't affect the unmanaged domain that VFIO manages explicitly. So VFIO will continue to use translation and userspace can't pass whatever it likes for the iova. Will