From: Matthew Wilcox <matthew@wil.cx>
To: Yu Zhao <yu.zhao@intel.com>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: [PATCH v10 6/7] PCI: document SR-IOV sysfs entries
Date: Fri, 6 Mar 2009 14:16:15 -0700 [thread overview]
Message-ID: <20090306211614.GI25995@parisc-linux.org> (raw)
In-Reply-To: <1235112888-9524-7-git-send-email-yu.zhao@intel.com>
Randy, can you wordsmith this one?
I think I'm starting to understand the difference between physfn and
dep_link, but an example would definitely help. It may or may not be
appropriate to put it in.
On Fri, Feb 20, 2009 at 02:54:47PM +0800, Yu Zhao wrote:
> 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 ceddcff..84dc100 100644
> --- a/Documentation/ABI/testing/sysfs-bus-pci
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -9,3 +9,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/.../virtfn/N
> +Date: February 2009
> +Contact: Yu Zhao <yu.zhao@intel.com>
> +Description:
> + This symbol link appears when hardware supports SR-IOV
> + capability and Physical Function driver has enabled it.
> + The symbol link points to the PCI device sysfs entry of
> + Virtual Function whose index is N (0...MaxVFs-1).
> +
> +What: /sys/bus/pci/devices/.../virtfn/dep_link
> +Date: February 2009
> +Contact: Yu Zhao <yu.zhao@intel.com>
> +Description:
> + This symbol link appears when hardware supports SR-IOV
> + capability and Physical Function driver has enabled it,
> + and this device has vendor specific dependencies with
> + others. The symbol link points to the PCI device sysfs
> + entry of Physical Function this device depends on.
> +
> +What: /sys/bus/pci/devices/.../physfn
> +Date: February 2009
> +Contact: Yu Zhao <yu.zhao@intel.com>
> +Description:
> + This symbol link appears when a device is Virtual Function.
> + The symbol link points to the PCI device sysfs entry of
> + Physical Function this device associates with.
> --
> 1.6.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-06 21:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:54 [PATCH v10 0/7] PCI: Linux kernel SR-IOV support Yu Zhao
2009-02-20 6:54 ` [PATCH v10 1/7] PCI: initialize and release SR-IOV capability Yu Zhao
2009-03-06 20:08 ` Matthew Wilcox
2009-03-06 22:03 ` Randy Dunlap
2009-03-06 23:31 ` Duyck, Alexander H
2009-03-07 2:38 ` Greg KH
2009-03-10 1:19 ` Yu Zhao
2009-03-11 4:36 ` Greg KH
2009-03-09 8:12 ` Yu Zhao
2009-02-20 6:54 ` [PATCH v10 2/7] PCI: restore saved SR-IOV state Yu Zhao
2009-03-06 20:09 ` Matthew Wilcox
2009-02-20 6:54 ` [PATCH v10 3/7] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-03-06 20:20 ` Matthew Wilcox
2009-03-09 8:13 ` Yu Zhao
2009-03-09 18:09 ` Randy Dunlap
2009-03-09 18:11 ` Matthew Wilcox
2009-02-20 6:54 ` [PATCH v10 4/7] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-03-06 20:37 ` Matthew Wilcox
2009-03-06 21:48 ` Randy Dunlap
2009-03-09 8:29 ` Yu Zhao
2009-03-07 2:40 ` Greg KH
2009-03-09 8:25 ` Yu Zhao
2009-03-09 19:39 ` Greg KH
2009-03-10 1:37 ` Yu Zhao
2009-03-11 4:34 ` Greg KH
2009-02-20 6:54 ` [PATCH v10 5/7] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-03-06 21:13 ` Matthew Wilcox
2009-03-09 8:28 ` Yu Zhao
2009-02-20 6:54 ` [PATCH v10 6/7] PCI: document SR-IOV sysfs entries Yu Zhao
2009-03-06 21:16 ` Matthew Wilcox [this message]
2009-03-06 22:35 ` Randy Dunlap
2009-02-20 6:54 ` [PATCH v10 7/7] PCI: manual for SR-IOV user and driver developer Yu Zhao
2009-03-06 21:17 ` Matthew Wilcox
2009-02-24 10:47 ` [PATCH v10 0/7] PCI: Linux kernel SR-IOV support Avi Kivity
2009-02-25 1:36 ` Yu Zhao
2009-03-06 19:33 ` Matthew Wilcox
2009-03-08 14:30 ` Avi Kivity
2009-03-08 15:01 ` Matthew Wilcox
2009-03-09 0:45 ` Greg KH
2009-03-09 3:42 ` Yang, Sheng
2009-03-09 4:35 ` Yang, Sheng
2009-03-09 13:45 ` Avi Kivity
2009-03-06 19:44 ` Matthew Wilcox
2009-03-07 2:34 ` Greg KH
2009-03-10 1:11 ` 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=20090306211614.GI25995@parisc-linux.org \
--to=matthew@wil.cx \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=yu.zhao@intel.com \
/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