From: Yu Zhao <yu.zhao@intel.com>
To: jbarnes@virtuousgeek.org
Cc: linux-pci@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Yu Zhao <yu.zhao@intel.com>
Subject: [PATCH v12 7/8] PCI: document SR-IOV sysfs entries
Date: Fri, 20 Mar 2009 11:25:17 +0800 [thread overview]
Message-ID: <1237519518-24048-8-git-send-email-yu.zhao@intel.com> (raw)
In-Reply-To: <1237519518-24048-1-git-send-email-yu.zhao@intel.com>
Reviewed-by: Randy Dunlap <rdunlap@xenotime.net>
Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Yu Zhao <yu.zhao@intel.com>
---
Documentation/ABI/testing/sysfs-bus-pci | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
index e638e15..36edf03 100644
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@@ -52,3 +52,30 @@ Description:
that some devices may have malformatted data. If the
underlying VPD has a writable section then the
corresponding section of this file will be writable.
+
+What: /sys/bus/pci/devices/.../virtfnN
+Date: March 2009
+Contact: Yu Zhao <yu.zhao@intel.com>
+Description:
+ This symbolic link appears when hardware supports the SR-IOV
+ capability and the Physical Function driver has enabled it.
+ The symbolic link points to the PCI device sysfs entry of the
+ Virtual Function whose index is N (0...MaxVFs-1).
+
+What: /sys/bus/pci/devices/.../dep_link
+Date: March 2009
+Contact: Yu Zhao <yu.zhao@intel.com>
+Description:
+ This symbolic link appears when hardware supports the SR-IOV
+ capability and the Physical Function driver has enabled it,
+ and this device has vendor specific dependencies with others.
+ The symbolic link points to the PCI device sysfs entry of
+ Physical Function this device depends on.
+
+What: /sys/bus/pci/devices/.../physfn
+Date: March 2009
+Contact: Yu Zhao <yu.zhao@intel.com>
+Description:
+ This symbolic link appears when a device is a Virtual Function.
+ The symbolic link points to the PCI device sysfs entry of the
+ Physical Function this device associates with.
--
1.5.6.4
next prev parent reply other threads:[~2009-03-20 3:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 3:25 [PATCH v12 0/8] PCI: Linux kernel SR-IOV support Yu Zhao
2009-03-20 3:25 ` [PATCH v12 1/8] PCI: initialize and release SR-IOV capability Yu Zhao
2009-03-20 17:54 ` Jesse Barnes
2009-03-21 14:05 ` Yu Zhao
2009-03-26 22:50 ` Jesse Barnes
2009-03-20 3:25 ` [PATCH v12 2/8] PCI: restore saved SR-IOV state Yu Zhao
2009-03-20 3:25 ` [PATCH v12 3/8] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-03-20 3:25 ` [PATCH v12 4/8] PCI: centralize device setup code Yu Zhao
2009-03-20 3:25 ` [PATCH v12 5/8] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-03-20 3:25 ` [PATCH v12 6/8] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-03-20 3:25 ` Yu Zhao [this message]
2009-03-20 16:32 ` [PATCH v12 7/8] PCI: document SR-IOV sysfs entries Chetan.Loke
2009-03-20 3:25 ` [PATCH v12 8/8] PCI: manual for SR-IOV user and driver developer Yu Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1237519518-24048-8-git-send-email-yu.zhao@intel.com \
--to=yu.zhao@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®