Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4041747ybg; Fri, 25 Oct 2019 12:28:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqwtFX5MP7T7JspJeoEbq8TJ6Yy+e9eyuV9fUIYj7GtQhZJRk5ffWoqrhhrXdWmC0DijvWqj X-Received: by 2002:aa7:de08:: with SMTP id h8mr5632195edv.169.1572031728394; Fri, 25 Oct 2019 12:28:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572031728; cv=none; d=google.com; s=arc-20160816; b=k9JZzx7XwWDPaTe1nDPpG7LgpTpzbac+4vW6phwBwKCBtEIWCURbuxZvcal0SuM66Y omcOMRHpD3VudK4QM48XmUpVQO/98ypkQpoe2JT3lYW9p3DybJFZucF1dmbTMpDeUej+ GNIJMEhIW8Vv+DbbCBUl88hzzHG2r1ThyvUYg1BPBtGeEYZ+WIekOqzQLjTPxr1RKQmC xVA2ceOG3p6LZdYwCk7jvLV9EZQups7LOpBBPy7xYisbJ9szVb+Yy7IDaRmAEVZ0rBYN dY2rHIBBgstoaeA0A/yOvVp5IxCMXfpZHC7x9616njbksfwe7r3abvmw0rxIOq8OHPol ADxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :dlp-reaction:dlp-version:dlp-product:content-language :accept-language:in-reply-to:references:message-id:date:thread-index :thread-topic:subject:cc:to:from; bh=SLCNUR0r2Ry71yekyYx3GSLI4OJcrMl9oijDRDYMShs=; b=lPXlM/awHVZUQ4pDxdxonDF+cqam9eDLLZWHM6XQ7Hwyy0gChMSjdEb7IcFqKJbTmW LoBD+kHm+AT2SYDj9lmFAVpLHT+35AcPMA/eTH9rRW/dypQcJIQpo7G0uRN9gH2De00X nU8hYPvaENMjJn3Zds3di5Wkw/ltQrbKnHqIgBw4aUqXyvdMg17gSJCuCoyOZOTFfsem IK3hUiwDF7PHKqz2bAji95Du349Y4UrtYpOnq4YVNSZ1AsxHy56V8vNgjxYIBLaeRfuW KUktvC4cRL+UxGDr8iNLNGTjitaCoEYr3UeN20/Sj0+EQC+FD5YPWtQPSqb2dMb37eX8 MEUg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s17si1795920ejr.229.2019.10.25.12.28.24; Fri, 25 Oct 2019 12:28:48 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436604AbfJYH1b convert rfc822-to-8bit (ORCPT + 99 others); Fri, 25 Oct 2019 03:27:31 -0400 Received: from mga06.intel.com ([134.134.136.31]:27356 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389667AbfJYH1a (ORCPT ); Fri, 25 Oct 2019 03:27:30 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2019 00:27:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,227,1569308400"; d="scan'208";a="398685265" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 25 Oct 2019 00:27:29 -0700 Received: from fmsmsx152.amr.corp.intel.com (10.18.125.5) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 25 Oct 2019 00:27:29 -0700 Received: from shsmsx108.ccr.corp.intel.com (10.239.4.97) by FMSMSX152.amr.corp.intel.com (10.18.125.5) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 25 Oct 2019 00:27:28 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.166]) by SHSMSX108.ccr.corp.intel.com ([169.254.8.225]) with mapi id 14.03.0439.000; Fri, 25 Oct 2019 15:27:27 +0800 From: "Tian, Kevin" To: Jacob Pan , "iommu@lists.linux-foundation.org" , LKML , Joerg Roedel , "David Woodhouse" , Alex Williamson , Jean-Philippe Brucker CC: "Liu, Yi L" , "Raj, Ashok" , Christoph Hellwig , Lu Baolu , Jonathan Cameron , Eric Auger Subject: RE: [PATCH v7 11/11] iommu/vt-d: Add svm/sva invalidate function Thread-Topic: [PATCH v7 11/11] iommu/vt-d: Add svm/sva invalidate function Thread-Index: AQHViqRXy9Yx+C3oUEClzLBbVKfxc6dq9Gqw Date: Fri, 25 Oct 2019 07:27:26 +0000 Message-ID: References: <1571946904-86776-1-git-send-email-jacob.jun.pan@linux.intel.com> <1571946904-86776-12-git-send-email-jacob.jun.pan@linux.intel.com> In-Reply-To: <1571946904-86776-12-git-send-email-jacob.jun.pan@linux.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzI4NzY5M2UtMjQ5MS00ODYzLWI4OGUtMmEyODQ5YTk3NzAxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVGVEVE1zMENNaWpZZk1uZVZzZVF4RHZXSnVXSWJqaUJUTW9lcmNETlBLUnJhdEs5Sk1xTUxyVjVlazhYZ0VxVyJ9 dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > From: Jacob Pan [mailto:jacob.jun.pan@linux.intel.com] > Sent: Friday, October 25, 2019 3:55 AM > > When Shared Virtual Address (SVA) is enabled for a guest OS via > vIOMMU, we need to provide invalidation support at IOMMU API and > driver > level. This patch adds Intel VT-d specific function to implement > iommu passdown invalidate API for shared virtual address. > > The use case is for supporting caching structure invalidation > of assigned SVM capable devices. Emulated IOMMU exposes queue > invalidation capability and passes down all descriptors from the guest > to the physical IOMMU. specifically you may clarify that only invalidations related to first-level page table is passed down, because it's guest structure being bound to the first-level. other descriptors are emulated or translated into other necessary operations. > > The assumption is that guest to host device ID mapping should be > resolved prior to calling IOMMU driver. Based on the device handle, > host IOMMU driver can replace certain fields before submit to the > invalidation queue. what is device ID? it's a bit confusing term here. > > Signed-off-by: Jacob Pan > Signed-off-by: Ashok Raj > Signed-off-by: Liu, Yi L > --- > drivers/iommu/intel-iommu.c | 170 > ++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 170 insertions(+) > > diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c > index 5fab32fbc4b4..a73e76d6457a 100644 > --- a/drivers/iommu/intel-iommu.c > +++ b/drivers/iommu/intel-iommu.c > @@ -5491,6 +5491,175 @@ static void > intel_iommu_aux_detach_device(struct iommu_domain *domain, > aux_domain_remove_dev(to_dmar_domain(domain), dev); > } > > +/* > + * 2D array for converting and sanitizing IOMMU generic TLB granularity to > + * VT-d granularity. Invalidation is typically included in the unmap > operation > + * as a result of DMA or VFIO unmap. However, for assigned device where > guest > + * could own the first level page tables without being shadowed by QEMU. > In > + * this case there is no pass down unmap to the host IOMMU as a result of > unmap > + * in the guest. Only invalidations are trapped and passed down. > + * In all cases, only first level TLB invalidation (request with PASID) can be > + * passed down, therefore we do not include IOTLB granularity for request > + * without PASID (second level). > + * > + * For an example, to find the VT-d granularity encoding for IOTLB > + * type and page selective granularity within PASID: > + * X: indexed by iommu cache type > + * Y: indexed by enum iommu_inv_granularity > + * [IOMMU_CACHE_INV_TYPE_IOTLB][IOMMU_INV_GRANU_ADDR] > + * > + * Granu_map array indicates validity of the table. 1: valid, 0: invalid > + * > + */ > +const static int > inv_type_granu_map[IOMMU_CACHE_INV_TYPE_NR][IOMMU_INV_GRAN > U_NR] = { > + /* PASID based IOTLB, support PASID selective and page selective */ > + {0, 1, 1}, > + /* PASID based dev TLBs, only support all PASIDs or single PASID */ > + {1, 1, 0}, I forgot previous discussion. is it necessary to pass down dev TLB invalidation requests? Can it be handled by host iOMMU driver automatically? > + /* PASID cache */ > + {1, 1, 0} > +}; > + > +const static u64 > inv_type_granu_table[IOMMU_CACHE_INV_TYPE_NR][IOMMU_INV_GRAN > U_NR] = { > + /* PASID based IOTLB */ > + {0, QI_GRAN_NONG_PASID, QI_GRAN_PSI_PASID}, > + /* PASID based dev TLBs */ > + {QI_DEV_IOTLB_GRAN_ALL, QI_DEV_IOTLB_GRAN_PASID_SEL, 0}, > + /* PASID cache */ > + {QI_PC_ALL_PASIDS, QI_PC_PASID_SEL, 0}, > +}; > + > +static inline int to_vtd_granularity(int type, int granu, u64 *vtd_granu) > +{ > + if (type >= IOMMU_CACHE_INV_TYPE_NR || granu >= > IOMMU_INV_GRANU_NR || > + !inv_type_granu_map[type][granu]) > + return -EINVAL; > + > + *vtd_granu = inv_type_granu_table[type][granu]; > + > + return 0; > +} > + > +static inline u64 to_vtd_size(u64 granu_size, u64 nr_granules) > +{ > + u64 nr_pages = (granu_size * nr_granules) >> VTD_PAGE_SHIFT; > + > + /* VT-d size is encoded as 2^size of 4K pages, 0 for 4k, 9 for 2MB, > etc. > + * IOMMU cache invalidate API passes granu_size in bytes, and > number of > + * granu size in contiguous memory. > + */ > + return order_base_2(nr_pages); > +} > + > +#ifdef CONFIG_INTEL_IOMMU_SVM > +static int intel_iommu_sva_invalidate(struct iommu_domain *domain, > + struct device *dev, struct iommu_cache_invalidate_info > *inv_info) > +{ > + struct dmar_domain *dmar_domain = to_dmar_domain(domain); > + struct device_domain_info *info; > + struct intel_iommu *iommu; > + unsigned long flags; > + int cache_type; > + u8 bus, devfn; > + u16 did, sid; > + int ret = 0; > + u64 size; > + > + if (!inv_info || !dmar_domain || > + inv_info->version != > IOMMU_CACHE_INVALIDATE_INFO_VERSION_1) > + return -EINVAL; > + > + if (!dev || !dev_is_pci(dev)) > + return -ENODEV; > + > + iommu = device_to_iommu(dev, &bus, &devfn); > + if (!iommu) > + return -ENODEV; > + > + spin_lock_irqsave(&device_domain_lock, flags); > + spin_lock(&iommu->lock); > + info = iommu_support_dev_iotlb(dmar_domain, iommu, bus, > devfn); > + if (!info) { > + ret = -EINVAL; > + goto out_unlock; > + } > + did = dmar_domain->iommu_did[iommu->seq_id]; > + sid = PCI_DEVID(bus, devfn); > + size = to_vtd_size(inv_info->addr_info.granule_size, inv_info- > >addr_info.nb_granules); > + > + for_each_set_bit(cache_type, (unsigned long *)&inv_info->cache, > IOMMU_CACHE_INV_TYPE_NR) { > + u64 granu = 0; > + u64 pasid = 0; > + > + ret = to_vtd_granularity(cache_type, inv_info->granularity, > &granu); > + if (ret) { > + pr_err("Invalid cache type and granu > combination %d/%d\n", cache_type, > + inv_info->granularity); > + break; > + } > + > + /* PASID is stored in different locations based on > granularity */ > + if (inv_info->granularity == IOMMU_INV_GRANU_PASID) > + pasid = inv_info->pasid_info.pasid; > + else if (inv_info->granularity == IOMMU_INV_GRANU_ADDR) > + pasid = inv_info->addr_info.pasid; > + else { > + pr_err("Cannot find PASID for given cache type and > granularity\n"); > + break; > + } > + > + switch (BIT(cache_type)) { > + case IOMMU_CACHE_INV_TYPE_IOTLB: > + if (size && (inv_info->addr_info.addr & > ((BIT(VTD_PAGE_SHIFT + size)) - 1))) { > + pr_err("Address out of range, 0x%llx, size > order %llu\n", > + inv_info->addr_info.addr, size); > + ret = -ERANGE; > + goto out_unlock; > + } > + > + qi_flush_piotlb(iommu, did, > mm_to_dma_pfn(inv_info->addr_info.addr), > + pasid, size, granu, inv_info- > >addr_info.flags & IOMMU_INV_ADDR_FLAGS_LEAF); > + > + /* > + * Always flush device IOTLB if ATS is enabled since > guest > + * vIOMMU exposes CM = 1, no device IOTLB flush > will be passed > + * down. > + */ > + if (info->ats_enabled) { > + qi_flush_dev_piotlb(iommu, sid, info->pfsid, > + pasid, info->ats_qdep, > + inv_info->addr_info.addr, > size, > + granu); > + } > + break; > + case IOMMU_CACHE_INV_TYPE_DEV_IOTLB: > + if (info->ats_enabled) { > + qi_flush_dev_piotlb(iommu, sid, info->pfsid, > + inv_info->addr_info.pasid, > info->ats_qdep, > + inv_info->addr_info.addr, > size, > + granu); > + } else > + pr_warn("Passdown device IOTLB flush w/o > ATS!\n"); > + > + break; > + case IOMMU_CACHE_INV_TYPE_PASID: > + qi_flush_pasid_cache(iommu, did, granu, inv_info- > >pasid_info.pasid); > + > + break; > + default: > + dev_err(dev, "Unsupported IOMMU invalidation > type %d\n", > + cache_type); > + ret = -EINVAL; > + } > + } > +out_unlock: > + spin_unlock(&iommu->lock); > + spin_unlock_irqrestore(&device_domain_lock, flags); > + > + return ret; > +} > +#endif > + > static int intel_iommu_map(struct iommu_domain *domain, > unsigned long iova, phys_addr_t hpa, > size_t size, int iommu_prot) > @@ -6027,6 +6196,7 @@ const struct iommu_ops intel_iommu_ops = { > .is_attach_deferred = intel_iommu_is_attach_deferred, > .pgsize_bitmap = INTEL_IOMMU_PGSIZES, > #ifdef CONFIG_INTEL_IOMMU_SVM > + .cache_invalidate = intel_iommu_sva_invalidate, > .sva_bind_gpasid = intel_svm_bind_gpasid, > .sva_unbind_gpasid = intel_svm_unbind_gpasid, > #endif > -- > 2.7.4