public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Zhao, Yu" <yu.zhao@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	kvm@vger.kernel.org, xen-devel@lists.xensource.com,
	virtualization@lists.linux-foundation.org
Subject: Re: SR-IOV: patches are available for Linux kernel [4/4]
Date: Thu, 14 Aug 2008 05:12:45 -0700	[thread overview]
Message-ID: <20080814121245.GB31927@kroah.com> (raw)
In-Reply-To: <7A25B56E4BE99C4283EB931CD1A40E1101686518@pdsmsx414.ccr.corp.intel.com>

On Thu, Aug 14, 2008 at 03:50:26PM +0800, Zhao, Yu wrote:
> On Thursday, August 14, 2008 7:46 AM, Greg KH <mailto:greg@kroah.com> wrote:
> > On Wed, Aug 13, 2008 at 01:09:16PM -0700, Randy Dunlap wrote:
> >> On Tue, 12 Aug 2008 16:46:39 +0800 Zhao, Yu wrote:
> >> 
> >>> [PATCH 4/4] PCI: document SR-IOV
> >>> 
> >>> SR-IOV Documentation.
> >>> 
> >>> Signed-off-by: Yu Zhao <yu.zhao@intel.com>
> >>> Signed-off-by:  Eddie Dong <eddie.dong@intel.com>
> >>> 
> >>> ---
> >>>  Documentation/ABI/testing/sysfs-bus-pci |   13 ++
> >>>  Documentation/PCI/00-INDEX              |    2
> >>>  Documentation/PCI/pci-iov-howto.txt     |  170
> > +++++++++++++++++++++++++++++++
> >>>  3 files changed, 185 insertions(+), 0 deletions(-)
> >>> 
> >>> diff --git a/Documentation/ABI/testing/sysfs-bus-pci
> > b/Documentation/ABI/testing/sysfs-bus-pci
> >>> index ceddcff..9ada27b 100644
> >>> --- a/Documentation/ABI/testing/sysfs-bus-pci
> >>> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> >>> @@ -9,3 +9,16 @@ 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/.../iov
> >>> +Date:		August 2008
> >>> +Contact:	Yu Zhao <yu.zhao@intel.com>
> >>> +Description:
> >>> +		This file will appear when SR-IOV capability is enabled
> >>> +		by the device driver if supported. It holds number of
> >>> +		available Virtual Functions and Bus, Device, Function
> >>> +		number and status of these Virtual Functions that belong
> >>> +		to this device (Physical Function). This file can be
> >> 
> >> This one file contains available VFs, Bus:dev:Func number, and
> >> status? Sounds like a misuse (abuse) of sysfs "one value per file"
> >> mantra, but I'll read below to see how it's done.
> >> 
> >> [added GregKH to cc: list]
> > 
> > I agree, why not just display the device tree of available devices
> > like all other busses do? 
> > 
> 
> Thanks for the comments. 
> 
> Will separate this file to
> /sys/bus/pci/devices/.../iov/{NumVFs,VF1,VF2,...}. The NumVFs file
> contains number of available VFs, and each VF file contains
> "bus:dev.func=status". Sounds better?

That sounds better yes.

Please use a 'struct device' for this as well, not a "raw" kobject.

thanks,

greg k-h

      reply	other threads:[~2008-08-14 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  8:46 SR-IOV: patches are available for Linux kernel [4/4] Zhao, Yu
2008-08-13 20:09 ` Randy Dunlap
2008-08-13 23:46   ` Greg KH
2008-08-14  7:50     ` Zhao, Yu
2008-08-14 12:12       ` Greg KH [this message]

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=20080814121245.GB31927@kroah.com \
    --to=greg@kroah.com \
    --cc=kvm@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    --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