mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yu Zhao <yu.zhao@intel.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 6/7] PCI: document SR-IOV sysfs entries
Date: Tue, 17 Feb 2009 20:50:21 +0800	[thread overview]
Message-ID: <20090217125021.GA2403@yzhao-otc.sh.intel.com> (raw)
In-Reply-To: <1234790920-1810-7-git-send-email-yu.zhao@intel.com>

Hi Greg,

The `struct device' is preferred over the `struct kobject' in all cases
that create subdirectory in sysfs, is this true?

I'd like to create a subdirectory under PCI device sysfs directory and
put some symbol links into that directory (only symbol links). Should I
use `device' or `kobject'? Currently I use `device' and get two extra
file/directory (uevent and power) which look like useless for my case
because this subdirectory doesn't reflect a real device.

I checked some code and found they use kobject_init_and_add(). Should
I use it instead, or keep using the `device'?

Please advise.

Regards,
Yu

On Mon, Feb 16, 2009 at 09:28:39PM +0800, Zhao, Yu 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.5.6.4
> 

  reply	other threads:[~2009-02-18  2:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 13:28 [PATCH v9 0/7] PCI: Linux kernel SR-IOV support Yu Zhao
2009-02-16 13:28 ` [PATCH v9 1/7] PCI: initialize and release SR-IOV capability Yu Zhao
2009-02-16 13:28 ` [PATCH v9 2/7] PCI: restore saved SR-IOV state Yu Zhao
2009-02-16 13:28 ` [PATCH v9 3/7] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-02-16 13:28 ` [PATCH v9 4/7] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-02-16 13:28 ` [PATCH v9 5/7] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-02-16 13:28 ` [PATCH v9 6/7] PCI: document SR-IOV sysfs entries Yu Zhao
2009-02-17 12:50   ` Yu Zhao [this message]
2009-02-17 13:01     ` Yu Zhao
2009-02-18  3:49     ` Greg KH
2009-02-17 14:43       ` Yu Zhao
2009-02-18  6:21         ` Greg KH
2009-02-17 17:01           ` Yu Zhao
2009-02-18  7:19             ` Greg KH
2009-02-17 19:21               ` Yu Zhao
2009-02-18 15:13                 ` Greg KH
2009-02-16 13:28 ` [PATCH v9 7/7] 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=20090217125021.GA2403@yzhao-otc.sh.intel.com \
    --to=yu.zhao@intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@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®