Received: by 2002:a17:90a:88:0:0:0:0 with SMTP id a8csp4426393pja; Thu, 21 Nov 2019 19:09:44 -0800 (PST) X-Google-Smtp-Source: APXvYqw+OkZjm3ZjbtPRwmFn6UKkMIIes1opiEC5uZNbeByIZ/sAfUcKoAJGtstZWuZ2zV2glddq X-Received: by 2002:a17:906:b25a:: with SMTP id ce26mr18681062ejb.13.1574392184872; Thu, 21 Nov 2019 19:09:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574392184; cv=none; d=google.com; s=arc-20160816; b=PnHLS63EshoMimUBpzat13yFfSEGOmciVWDeKUAa0G5GWwadRRabbw/IKezEogVIGu 24mT8lveWEKTz06AOeWEzFXMC0th8Ye8B1GnDO+bns9M6Nx1qVrrrTBBqryHrfly+Hna M2hCIyPOdvof9F05Scw2J5lzCy4VEwT6YzX6GZG4uKX12dX50o0bZXdTyb/uaCSxMR2S jwahmlKrZnFvPeQWwnL+wT1fc5CZmEu4RsIyJTW1lmu2Q4/aG9RvDVIIfTIunY0HwmHG +w4hj8QxnSlr0ES55NcaLuOwFzD2lnnwOV4qyrDpKTPZN7Xc6xHzjEuWSjmSbJ5sqWGq 05cw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=c9krxvTF9QyoCp/hV/u8HZGSiuYuiuRju2dfnFEyL6c=; b=cavtVgMM/H/ordnjSHmBNYy9VhUtv5NMRHYtlGdr8gbsHNCCvljJZhoYyfSaIXjZyt SfcyuylvjXjEUJtuq0aTrCCEKoH5nyCAqhjQNzRec8g93ezP6Aw1HvCshuBHElWVeGrE EEL57mYk99wW/Z3Gw6NJRGYWPB/D5Uc0QI11zXba0ws3envFRmtzCV+qNoHbpZvcNWrk 40ONskOxl4XyH7Q0qKrpntv7SaMYc1bgnzP1a8oRNOnEcUF+Uw8DlPSlKZ/SmSlPeYAR h0hnKetgSmr94seesOnnw4ateilfvljvfgdOCJirM61dj9dF+JCRaie8KDo9UdI2mFSp WfZA== 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 t8si4473178edd.373.2019.11.21.19.09.20; Thu, 21 Nov 2019 19:09:44 -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 S1726638AbfKVDIW (ORCPT + 99 others); Thu, 21 Nov 2019 22:08:22 -0500 Received: from mga14.intel.com ([192.55.52.115]:53712 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726335AbfKVDIW (ORCPT ); Thu, 21 Nov 2019 22:08:22 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Nov 2019 19:08:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,228,1571727600"; d="scan'208";a="232540432" Received: from allen-box.sh.intel.com ([10.239.159.136]) by fmsmga004.fm.intel.com with ESMTP; 21 Nov 2019 19:08:19 -0800 From: Lu Baolu To: Joerg Roedel Cc: David Woodhouse , ashok.raj@intel.com, jacob.jun.pan@linux.intel.com, kevin.tian@intel.com, Eric Auger , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Lu Baolu Subject: [PATCH 0/5] iommu/vt-d: Consolidate various cache flush ops Date: Fri, 22 Nov 2019 11:04:44 +0800 Message-Id: <20191122030449.28892-1-baolu.lu@linux.intel.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Best regards, Lu Baolu Lu Baolu (5): iommu/vt-d: Extend iommu_flush for scalable mode iommu/vt-d: Consolidate pasid cache invalidation iommu/vt-d: Consolidate device tlb invalidation iommu/vt-d: Consolidate pasid-based tlb invalidation iommu/vt-d: Consolidate pasid-based device tlb invalidation drivers/iommu/dmar.c | 61 --------- drivers/iommu/intel-iommu.c | 246 +++++++++++++++++++++++++++++------- drivers/iommu/intel-pasid.c | 39 +----- drivers/iommu/intel-svm.c | 60 ++------- include/linux/intel-iommu.h | 39 ++++-- 5 files changed, 244 insertions(+), 201 deletions(-) -- 2.17.1