Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2004122ybl; Tue, 3 Dec 2019 16:34:25 -0800 (PST) X-Google-Smtp-Source: APXvYqw8+9WaaDCMRJ/aGhcJp2xRUCSNrX8Nru26E7htvrIdnxGyuWfPhz9N2YUhK5wKk8AWyaWz X-Received: by 2002:aca:5f41:: with SMTP id t62mr178416oib.165.1575419665280; Tue, 03 Dec 2019 16:34:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575419665; cv=none; d=google.com; s=arc-20160816; b=xXR8H+n4X17TcRDrYAXibhzynzA/o7JQOXGXSbQNZXQpA8jLq5Kc4fRq8TBP9GhaOu 8QaxXgiFh7A9gX1WS78NeYKXV9w27/vV6HCOF5CKuU9xBJapYlBPvFuOterKR1mx9T08 xUSsZq0Qg+7vvRrcCMTmlxMydrOhYzXeIRv0dYv1vTThCWWKvwE0LkFJ4aLufHiB2qlW OHn+nv3KL3veYBTHaWjbDRx8cNjXBoTjZ55/W3E+1NxszLB9VvKIaegpHNvSVA6fPbNT 9ZgqtPnI8GIETI54qbH4rfF2UJ7fKXI9Z9aCF9mVZU0Nfcyq7MInV6GFznZhem1E8JNp 0v+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=aS490UTwYoS6K9MnQ8dNUTYXyreJKKLe4H8/6dpf550=; b=xkVVJxClelF1gWvN8LBeXuZkWob+kHy763KSMSNYnZw0T1+gd1vNemufXrz7IgmLhx 68p8oX1Z6DoAGzb/703ZHJRLUfctuxf1hDupca+Kqgx1TyoVG0sJRxgmxnAITY0krDmG kY47zC9xgyM3Btb2QhDYYndhvtdljm0l672zObSgrPOcolNt4faMMOvm3ilffQ0hlfLs hDbLVlYLgy94B+TScJxbGN7KYODDMbPGgQRw1jaXsYjFqaM/r8DdCCmy1AgRlj3RIgbN IskLui8dpZAOf1ZGS0ikIRWVcFtR3KsuRjX15s5ywWm6F9eYSXkclN02kV+9fzTjAhgH Sjpw== 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 j23si2211464otr.48.2019.12.03.16.34.11; Tue, 03 Dec 2019 16:34:25 -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; 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 S1726395AbfLDAc5 (ORCPT + 99 others); Tue, 3 Dec 2019 19:32:57 -0500 Received: from mga17.intel.com ([192.55.52.151]:29488 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726008AbfLDAc5 (ORCPT ); Tue, 3 Dec 2019 19:32:57 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2019 16:32:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,275,1571727600"; d="scan'208";a="223029646" Received: from allen-box.sh.intel.com (HELO [10.239.159.136]) ([10.239.159.136]) by orsmga002.jf.intel.com with ESMTP; 03 Dec 2019 16:32:54 -0800 Cc: baolu.lu@linux.intel.com, Joerg Roedel , David Woodhouse , ashok.raj@intel.com, kevin.tian@intel.com, Eric Auger , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] iommu/vt-d: Consolidate various cache flush ops To: Jacob Pan References: <20191122030449.28892-1-baolu.lu@linux.intel.com> <20191202120252.45606c47@jacob-builder> <20191203085026.1785292b@jacob-builder> From: Lu Baolu Message-ID: Date: Wed, 4 Dec 2019 08:32:17 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <20191203085026.1785292b@jacob-builder> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jacob, On 12/4/19 12:50 AM, Jacob Pan wrote: > On Tue, 3 Dec 2019 10:44:45 +0800 > Lu Baolu wrote: > >> Hi Jacob, >> >> On 12/3/19 4:02 AM, Jacob Pan wrote: >>> On Fri, 22 Nov 2019 11:04:44 +0800 >>> Lu Baolu wrote: >>> >>>> Intel VT-d 3.0 introduces more caches and interfaces for software >>>> to flush when it runs in the scalable mode. Currently various >>>> cache flush helpers are scattered around. This consolidates them >>>> by putting them in the existing iommu_flush structure. >>>> >>>> /* struct iommu_flush - Intel IOMMU cache invalidation ops >>>> * >>>> * @cc_inv: invalidate context cache >>>> * @iotlb_inv: Invalidate IOTLB and paging structure caches when >>>> software >>>> * has changed second-level tables. >>>> * @p_iotlb_inv: Invalidate IOTLB and paging structure caches when >>>> software >>>> * has changed first-level tables. >>>> * @pc_inv: invalidate pasid cache >>>> * @dev_tlb_inv: invalidate cached mappings used by >>>> requests-without-PASID >>>> * from the Device-TLB on a endpoint device. >>>> * @p_dev_tlb_inv: invalidate cached mappings used by >>>> requests-with-PASID >>>> * from the Device-TLB on an endpoint device >>>> */ >>>> struct iommu_flush { >>>> void (*cc_inv)(struct intel_iommu *iommu, u16 did, >>>> u16 sid, u8 fm, u64 type); >>>> void (*iotlb_inv)(struct intel_iommu *iommu, u16 did, u64 >>>> addr, unsigned int size_order, u64 type); >>>> void (*p_iotlb_inv)(struct intel_iommu *iommu, u16 did, >>>> u32 pasid, u64 addr, unsigned long npages, bool ih); >>>> void (*pc_inv)(struct intel_iommu *iommu, u16 did, u32 >>>> pasid, u64 granu); >>>> void (*dev_tlb_inv)(struct intel_iommu *iommu, u16 sid, >>>> u16 pfsid, u16 qdep, u64 addr, unsigned int mask); >>>> void (*p_dev_tlb_inv)(struct intel_iommu *iommu, u16 sid, >>>> u16 pfsid, u32 pasid, u16 qdep, u64 addr, >>>> unsigned long npages); >>>> }; >>>> >>>> The name of each cache flush ops is defined according to the spec >>>> section 6.5 so that people are easy to look up them in the spec. >>>> >>> Nice consolidation. For nested SVM, I also introduced cache flushed >>> helpers as needed. >>> https://lkml.org/lkml/2019/10/24/857 >>> >>> Should I wait for yours to be merged or you want to extend the this >>> consolidation after SVA/SVM cache flush? I expect to send my v8 >>> shortly. >> >> Please base your v8 patch on this series. So it could get more chances >> for test. >> > Sounds good. I am sorry I need to spend more time on this patch series. Please go ahead without it. Best regards, baolu > >> I will queue this patch series for internal test after 5.5-rc1 and if >> everything goes well, I will forward it to Joerg around rc4 for linux- >> next. >> >> Best regards, >> baolu > > [Jacob Pan] >