Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2716001yba; Mon, 6 May 2019 10:24:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqxxc4hnkyW8EaywalzTK8K3BkdWelPbsE80sC9H1x5d15bL4VBAaw54odVloRpZr4LaB7T4 X-Received: by 2002:a17:902:4503:: with SMTP id m3mr31188921pld.97.1557163449636; Mon, 06 May 2019 10:24:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557163449; cv=none; d=google.com; s=arc-20160816; b=kwF7h5REsrPpuNWvTbaq7lzG5dwQFPepLuJnE4zV8vMA4bYfatfKJZWcgLLBTTSbHx 0SjsUKG+0ToBeqZz59KJYRy/siVEjvfmGPJa/rmnIP+DyEs/uisV9qWWToryoKySmiSX qetNnRoSFoepadfWmcWdzJhAOu8lKG/KYjJBdFvhDemb9SuVLCmJ2RuB/M0N8k2TBQ6o lkDqjDbOkERZqwf5J2jse2u2ckMhJJHzeyVaz3GzZFVJGWE0ZJMkIrzx71VZSGLO1nbb N++boeSglL62UdhuVRIWBqjr+DCdU/5fZK+/ITJlGrpWKw5RQyb3wjxQFmTEyfkiaC7Z B+XA== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=6UuVE1DrbD6VSyi2y+kmCa/BIKjfqCLIXL2s97ct4/w=; b=Q0jryR2SyBrkzjiz0rKq5FzlJMgnfEpo5VV5hWueC8LOGijT2d6nDQdVsMmmKNsYxD 98E6Ztziyge17jq4N4Em59KunnAG72We22EHaWCOYWRqaTWfGJKYtYICERLZ0Rcj6xGo 61TyG+CdTbh5WWKDg3zT//W36WeBC9BhZUOwj33AOZHvKmvy2VecKPXCmqGiiO9LKT2o s0OKr4XsAwm7HlK16M76bHWrf8dXKZMo6m5NdTBzYUdcy59IDSEop9gjZtu/yk0JXOlp Rrg0qhoHNITYKRzL74maGAwDJXqy/lcbPfj78LDdnjKxPrG80fCfWUJaNgrpW7/fRfku OCgA== 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 f197si4444683pfa.276.2019.05.06.10.23.54; Mon, 06 May 2019 10:24:09 -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 S1726715AbfEFRWR (ORCPT + 99 others); Mon, 6 May 2019 13:22:17 -0400 Received: from mga07.intel.com ([134.134.136.100]:31139 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726393AbfEFRWR (ORCPT ); Mon, 6 May 2019 13:22:17 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 May 2019 10:22:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,438,1549958400"; d="scan'208";a="230014471" Received: from skuppusw-desk.jf.intel.com ([10.54.74.33]) by orsmga001.jf.intel.com with ESMTP; 06 May 2019 10:22:15 -0700 From: sathyanarayanan.kuppuswamy@linux.intel.com To: bhelgaas@google.com Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, ashok.raj@intel.com, keith.busch@intel.com, sathyanarayanan.kuppuswamy@linux.intel.com Subject: [PATCH v2 1/5] PCI/ATS: Add PRI support for PCIe VF devices Date: Mon, 6 May 2019 10:20:03 -0700 Message-Id: X-Mailer: git-send-email 2.20.1 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Kuppuswamy Sathyanarayanan When IOMMU tries to enable PRI for VF device in iommu_enable_dev_iotlb(), it always fails because PRI support for PCIe VF device is currently broken in PCIE driver. Current implementation expects the given PCIe device (PF & VF) to implement PRI capability before enabling the PRI support. But this assumption is incorrect. As per PCIe spec r4.0, sec 9.3.7.11, all VFs associated with PF can only use the Page Request Interface (PRI) of the PF and not implement it. Hence we need to create exception for handling the PRI support for PCIe VF device. Since PRI is shared between PF/VF devices, following rules should apply. 1. Enable PRI in VF only if its already enabled in PF. 2. When enabling/disabling PRI for VF, instead of configuring the registers just increase/decrease the usage count (pri_ref_cnt) of PF. 3. Disable PRI in PF only if pr_ref_cnt is zero. Cc: Ashok Raj Cc: Keith Busch Suggested-by: Ashok Raj Signed-off-by: Kuppuswamy Sathyanarayanan --- drivers/pci/ats.c | 53 +++++++++++++++++++++++++++++++++++++++++++-- include/linux/pci.h | 1 + 2 files changed, 52 insertions(+), 2 deletions(-) diff --git a/drivers/pci/ats.c b/drivers/pci/ats.c index 97c08146534a..5582e5d83a3f 100644 --- a/drivers/pci/ats.c +++ b/drivers/pci/ats.c @@ -181,12 +181,39 @@ int pci_enable_pri(struct pci_dev *pdev, u32 reqs) u16 control, status; u32 max_requests; int pos; + struct pci_dev *pf; if (WARN_ON(pdev->pri_enabled)) return -EBUSY; pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_PRI); - if (!pos) + + if (pdev->is_virtfn) { + /* + * Per PCIe r4.0, sec 9.3.7.11, VF must not implement PRI + * Capability. + */ + if (pos) { + dev_err(&pdev->dev, "VF must not implement PRI"); + return -EINVAL; + } + + pf = pci_physfn(pdev); + + /* If VF config does not match with PF, return error */ + if (!pf->pri_enabled) + return -EINVAL; + + pdev->pri_reqs_alloc = pf->pri_reqs_alloc; + pdev->pri_enabled = 1; + + /* Increment PF PRI refcount */ + atomic_inc(&pf->pri_ref_cnt); + + return 0; + } + + if (pdev->is_physfn && !pos) return -EINVAL; pci_read_config_word(pdev, pos + PCI_PRI_STATUS, &status); @@ -202,7 +229,6 @@ int pci_enable_pri(struct pci_dev *pdev, u32 reqs) pci_write_config_word(pdev, pos + PCI_PRI_CTRL, control); pdev->pri_enabled = 1; - return 0; } EXPORT_SYMBOL_GPL(pci_enable_pri); @@ -217,10 +243,27 @@ void pci_disable_pri(struct pci_dev *pdev) { u16 control; int pos; + struct pci_dev *pf; if (WARN_ON(!pdev->pri_enabled)) return; + /* All VFs should be disabled before disabling PF */ + if (atomic_read(&pdev->pri_ref_cnt)) + return; + + if (pdev->is_virtfn) { + /* Since VF shares PRI with PF, use PF config. */ + pf = pci_physfn(pdev); + + /* Decrement PF PRI refcount */ + atomic_dec(&pf->pri_ref_cnt); + + pdev->pri_enabled = 0; + + return; + } + pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_PRI); if (!pos) return; @@ -246,6 +289,9 @@ void pci_restore_pri_state(struct pci_dev *pdev) if (!pdev->pri_enabled) return; + if (pdev->is_virtfn) + return; + pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_PRI); if (!pos) return; @@ -270,6 +316,9 @@ int pci_reset_pri(struct pci_dev *pdev) if (WARN_ON(pdev->pri_enabled)) return -EBUSY; + if (pdev->is_virtfn) + return 0; + pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_PRI); if (!pos) return -EINVAL; diff --git a/include/linux/pci.h b/include/linux/pci.h index 77448215ef5b..699c79c99a39 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -450,6 +450,7 @@ struct pci_dev { #endif #ifdef CONFIG_PCI_PRI u32 pri_reqs_alloc; /* Number of PRI requests allocated */ + atomic_t pri_ref_cnt; /* Number of VFs with PRI enabled */ #endif #ifdef CONFIG_PCI_PASID u16 pasid_features; -- 2.20.1