Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp713178ybl; Wed, 4 Dec 2019 09:38:46 -0800 (PST) X-Google-Smtp-Source: APXvYqyM2NPIgnkkkX1RohEtm4EzXXY62peOwSkDJ8ThNIMcEBvEqk1HsWRGnTyleoAYtTT1IUOp X-Received: by 2002:a05:6830:1615:: with SMTP id g21mr3574204otr.49.1575481126582; Wed, 04 Dec 2019 09:38:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575481126; cv=none; d=google.com; s=arc-20160816; b=XHyKkd/OKSz5xF2KC/WNOye4A4IpXm6egHT/vtS5P6vQj3eK7Mh3SO5JAtSAha4JiJ 48jLDm9/H3SQuwPlmiN+rXtJuxCr+Q+B7YqmMEST1nbeQdjhyNSxiM7UdpPnKmx+HtY3 C5eyzz0b1P4YbcbwLjweLcPYNEH7OpfY+V73s2peB8ti0Qmf96W770e0SVEN9sWj7X3I nCXO3/Ve6sSoRMaEtfpkbl2fz1tMLOuS9Ktqgu+S2kTAqQFn17nDlHnh3ErJ0E1GIX6J SyAESt1N1WRhpD+V7vsYskoMn9n6zsD05a3HwT46RiFXPYssUnPzMlNvQbBpLssAmBsc VG4A== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=jQsH2aVmO692RDIYTiwfOQ+/47gKnWxnrSRTtSNsVOI=; b=Wwp3H90cv3a3t5UWRWN5kY3TPEcU09ZOQ5IYgcPMcIFNGhip/kT9H7U6R7jiWPiMHU NTBTzObReAyoWggxYTnn7xZRLMm2gpgqFVDApksc14LU8Ni9AGpn3Xxa4TAbshvp7D6l G16CVMzzJM99b2hz653n03QvjBrmrCwVM26F3k7l8X3Zl/5GC3UwaOkpZXkhaua0i6ND mzTXMnYJAxyl0cqKPm1AkBrwYGYGI5crF37Ja14RY9AYVm7WydO067rdlKucEM6Y/BAa UV2t+btkRxIA/bnquTCy6RV4K6QhTcm6fKqwZmi68k90a5J/nSPIdYnwtrMOb/RlXt5V ah/A== 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 l6si3463241oti.249.2019.12.04.09.38.32; Wed, 04 Dec 2019 09:38:46 -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 S1728031AbfLDRhQ (ORCPT + 99 others); Wed, 4 Dec 2019 12:37:16 -0500 Received: from mga06.intel.com ([134.134.136.31]:43219 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727033AbfLDRhQ (ORCPT ); Wed, 4 Dec 2019 12:37:16 -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 orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Dec 2019 09:37:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,278,1571727600"; d="scan'208";a="223306093" Received: from jacob-builder.jf.intel.com (HELO jacob-builder) ([10.7.199.155]) by orsmga002.jf.intel.com with ESMTP; 04 Dec 2019 09:37:15 -0800 Date: Wed, 4 Dec 2019 09:41:59 -0800 From: Jacob Pan To: Lu Baolu Cc: Joerg Roedel , David Woodhouse , ashok.raj@intel.com, kevin.tian@intel.com, Eric Auger , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, jacob.jun.pan@linux.intel.com Subject: Re: [PATCH 0/5] iommu/vt-d: Consolidate various cache flush ops Message-ID: <20191204094159.7b3e4100@jacob-builder> In-Reply-To: References: <20191122030449.28892-1-baolu.lu@linux.intel.com> <20191202120252.45606c47@jacob-builder> <20191203085026.1785292b@jacob-builder> Organization: OTC X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 4 Dec 2019 08:32:17 +0800 Lu Baolu wrote: > 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. > NP, let me know when you need testing.