| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1629291717-38564-6-git-send-email-liudongdong3@huawei.com>
Date: Wed, 18 Aug 2021 21:01:54 +0800
From: Dongdong Liu <liudongdong3@...wei.com>
To: <helgaas@...nel.org>, <hch@...radead.org>, <kw@...ux.com>,
<logang@...tatee.com>, <leon@...nel.org>,
<linux-pci@...r.kernel.org>, <rajur@...lsio.com>,
<hverkuil-cisco@...all.nl>
CC: <linux-media@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: [PATCH V8 5/8] PCI/IOV: Add 10-Bit Tag sysfs files for VF devices
PCIe spec 5.0 r1.0 section 2.2.6.2 says:
If an Endpoint supports sending Requests to other Endpoints (as
opposed to host memory), the Endpoint must not send 10-Bit Tag
Requests to another given Endpoint unless an implementation-specific
mechanism determines that the Endpoint supports 10-Bit Tag Completer
capability.
Add sriov_vf_10bit_tag file to query the status of VF 10-Bit Tag
Requester Enable.
Add a sriov_vf_10bit_tag_ctl sysfs file, write 0 to disable the VF
10-Bit Tag Requester. The typical use case is for p2pdma when the peer
device does not support 10-Bit Tag Completer. Write 1 to enable 10-Bit
Tag Requester when RC supports 10-Bit Tag Completer capability. The
typical use case is for host memory targeted by DMA Requests.
Signed-off-by: Dongdong Liu <liudongdong3@...wei.com>
---
Documentation/ABI/testing/sysfs-bus-pci | 23 ++++++++++++++
drivers/pci/iov.c | 54 +++++++++++++++++++++++++++++++++
2 files changed, 77 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
index 759682f..692bf65 100644
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@@ -423,3 +423,26 @@ Description:
10-Bit Tag Completer. Write 1 to enable 10-Bit Tag Requester
when RC supports 10-Bit Tag Completer capability. The typical
use case is for host memory targeted by DMA Requests.
+
+What: /sys/bus/pci/devices/.../sriov_vf_10bit_tag
+Date: August 2021
+Contact: Dongdong Liu <liudongdong3@...wei.com>
+Description:
+ This file is associated with a SR-IOV physical function (PF).
+ It is visible when the device supports VF 10-Bit Tag Requester.
+ It contains the status of VF 10-Bit Tag Requester Enable.
+ The file is read-only.
+
+What: /sys/bus/pci/devices/.../sriov_vf_10bit_tag_ctl
+Date: August 2021
+Contact: Dongdong Liu <liudongdong3@...wei.com>
+Description:
+ This file is associated with a SR-IOV virtual function (VF).
+ It is visible when the device supports VF 10-Bit Tag
+ Requester. The file is only writeable when the VF driver
+ does not bind to a device. Write 0 to any VF's file disables
+ 10-Bit Tag Requester for all VFs. The typical use case is for
+ p2pdma when the peer device does not support 10-Bit Tag
+ Completer. Write 1 to enable 10-Bit Tag Requester for all VFs
+ when RC supports 10-Bit Tag Completer capability. The typical
+ use case is for host memory targeted by DMA Requests.
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index dafdc65..bf15b33 100644
--- a/drivers/pci/iov.c
+++ b/drivers/pci/iov.c
@@ -220,10 +220,42 @@ static ssize_t sriov_vf_msix_count_store(struct device *dev,
static DEVICE_ATTR_WO(sriov_vf_msix_count);
#endif
+
+static ssize_t sriov_vf_10bit_tag_ctl_store(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct pci_dev *vf_dev = to_pci_dev(dev);
+ struct pci_dev *pdev = pci_physfn(vf_dev);
+ bool enable;
+
+ if (kstrtobool(buf, &enable) < 0)
+ return -EINVAL;
+
+ if (vf_dev->driver)
+ return -EBUSY;
+
+ if (enable) {
+ if (!pcie_rp_10bit_tag_cmp_supported(pdev))
+ return -EPERM;
+
+ pdev->sriov->ctrl |= PCI_SRIOV_CTRL_VF_10BIT_TAG_REQ_EN;
+ } else {
+ pdev->sriov->ctrl &= ~PCI_SRIOV_CTRL_VF_10BIT_TAG_REQ_EN;
+ }
+
+ pci_write_config_word(pdev, pdev->sriov->pos + PCI_SRIOV_CTRL,
+ pdev->sriov->ctrl);
+
+ return count;
+}
+static DEVICE_ATTR_WO(sriov_vf_10bit_tag_ctl);
+
static struct attribute *sriov_vf_dev_attrs[] = {
#ifdef CONFIG_PCI_MSI
&dev_attr_sriov_vf_msix_count.attr,
#endif
+ &dev_attr_sriov_vf_10bit_tag_ctl.attr,
NULL,
};
@@ -236,6 +268,11 @@ static umode_t sriov_vf_attrs_are_visible(struct kobject *kobj,
if (!pdev->is_virtfn)
return 0;
+ pdev = pci_physfn(pdev);
+ if ((a == &dev_attr_sriov_vf_10bit_tag_ctl.attr) &&
+ !(pdev->sriov->cap & PCI_SRIOV_CAP_VF_10BIT_TAG_REQ))
+ return 0;
+
return a->mode;
}
@@ -487,12 +524,23 @@ static ssize_t sriov_drivers_autoprobe_store(struct device *dev,
return count;
}
+static ssize_t sriov_vf_10bit_tag_show(struct device *dev,
+ struct device_attribute *attr,
+ char *buf)
+{
+ struct pci_dev *pdev = to_pci_dev(dev);
+
+ return sysfs_emit(buf, "%u\n",
+ !!(pdev->sriov->ctrl & PCI_SRIOV_CTRL_VF_10BIT_TAG_REQ_EN));
+}
+
static DEVICE_ATTR_RO(sriov_totalvfs);
static DEVICE_ATTR_RW(sriov_numvfs);
static DEVICE_ATTR_RO(sriov_offset);
static DEVICE_ATTR_RO(sriov_stride);
static DEVICE_ATTR_RO(sriov_vf_device);
static DEVICE_ATTR_RW(sriov_drivers_autoprobe);
+static DEVICE_ATTR_RO(sriov_vf_10bit_tag);
static struct attribute *sriov_pf_dev_attrs[] = {
&dev_attr_sriov_totalvfs.attr,
@@ -501,6 +549,7 @@ static struct attribute *sriov_pf_dev_attrs[] = {
&dev_attr_sriov_stride.attr,
&dev_attr_sriov_vf_device.attr,
&dev_attr_sriov_drivers_autoprobe.attr,
+ &dev_attr_sriov_vf_10bit_tag.attr,
#ifdef CONFIG_PCI_MSI
&dev_attr_sriov_vf_total_msix.attr,
#endif
@@ -511,10 +560,15 @@ static umode_t sriov_pf_attrs_are_visible(struct kobject *kobj,
struct attribute *a, int n)
{
struct device *dev = kobj_to_dev(kobj);
+ struct pci_dev *pdev = to_pci_dev(dev);
if (!dev_is_pf(dev))
return 0;
+ if ((a == &dev_attr_sriov_vf_10bit_tag.attr) &&
+ !(pdev->sriov->cap & PCI_SRIOV_CAP_VF_10BIT_TAG_REQ))
+ return 0;
+
return a->mode;
}
--
2.7.4
Powered by blists - more mailing lists