WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] RE: SR-IOV: patches are available for Linux kernel [4/4]

To: "Randy Dunlap" <randy.dunlap@xxxxxxxxxx>
Subject: [Xen-devel] RE: SR-IOV: patches are available for Linux kernel [4/4]
From: "Zhao, Yu" <yu.zhao@xxxxxxxxx>
Date: Thu, 14 Aug 2008 15:50:26 +0800
Cc: Greg KH <greg@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Aug 2008 00:50:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080813234620.GB32154@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <7A25B56E4BE99C4283EB931CD1A40E110164BC9B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080813130916.3bf3bc0c.randy.dunlap@xxxxxxxxxx> <20080813234620.GB32154@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acj9n/vy2Uao4lVZSwCWEC40wOZ77AAP7xOA
Thread-topic: SR-IOV: patches are available for Linux kernel [4/4]
On Thursday, August 14, 2008 7:46 AM, Greg KH <mailto:greg@xxxxxxxxx> 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@xxxxxxxxx>
>>> Signed-off-by:  Eddie Dong <eddie.dong@xxxxxxxxx>
>>> 
>>> ---
>>>  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@xxxxxxxxx>
>>> +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?

> thanks,
> 
> greg k-h


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>