On Wed, Nov 05, 2008 at 08:33:18PM -0800, Greg KH wrote: > On Wed, Oct 22, 2008 at 04:45:15PM +0800, Yu Zhao wrote: > > Document the SR-IOV sysfs entries. > > > > Cc: Alex Chiang <[EMAIL PROTECTED]> > > Cc: Grant Grundler <[EMAIL PROTECTED]> > > Cc: Greg KH <[EMAIL PROTECTED]> > > Cc: Ingo Molnar <[EMAIL PROTECTED]> > > Cc: Jesse Barnes <[EMAIL PROTECTED]> > > Cc: Matthew Wilcox <[EMAIL PROTECTED]> > > Cc: Randy Dunlap <[EMAIL PROTECTED]> > > Cc: Roland Dreier <[EMAIL PROTECTED]> > > Signed-off-by: Yu Zhao <[EMAIL PROTECTED]> > > > > --- > > Documentation/ABI/testing/sysfs-bus-pci | 33 > > +++++++++++++++++++++++++++++++ > > 1 files changed, 33 insertions(+), 0 deletions(-) > > > > diff --git a/Documentation/ABI/testing/sysfs-bus-pci > > b/Documentation/ABI/testing/sysfs-bus-pci > > index ceddcff..41cce8f 100644 > > --- a/Documentation/ABI/testing/sysfs-bus-pci > > +++ b/Documentation/ABI/testing/sysfs-bus-pci > > @@ -9,3 +9,36 @@ 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/enable > > Are you sure this is still the correct location with your change to > struct device?
Nevermind, this is correct. But the bigger problem is that userspace doesn't know when these attributes show up. So tools like udev and HAL and others can't look for them as they never get notified, and they don't even know if they should be looking for them or not. Is there any way to tie these attributes to the "main" pci device so that they get created before the device is announced to the world? Doing that would solve this issue. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
