[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FF3EC130E@rrsmsx501.amr.corp.intel.com>
Date: Tue, 1 Jun 2010 12:57:18 -0600
From: "Williams, Mitch A" <mitch.a.williams@...el.com>
To: Greg KH <greg@...ah.com>, Frank Pan <frankpzh@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
Yu Zhao <yu.zhao@...el.com>,
Chris Wright <chrisw@...s-sol.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"David S. Miller" <davem@...emloft.net>,
Matt Carlson <mcarlson@...adcom.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Add a helper function in PCI IOV to get VF device
>-----Original Message-----
>From: Greg KH [mailto:greg@...ah.com]
>Sent: Tuesday, June 01, 2010 11:39 AM
>
>On Tue, Jun 01, 2010 at 01:05:25PM +0800, Frank Pan wrote:
>> Greetings,
>>
>> The motivation is make VF device visible to PF driver. PF driver
>> may need this to access VF's PCI configuration.
>
>What is "VF" and "PF" here?
>
>> Another use case is in sysfs symbolic linking. Some of VF's sysfs
>> entries are created by PF driver. For example, /sys/class/net/ethx/vfx
>> in Intel 82576 NIC driver. Makeing a symbolic link from VF's pci device
>> to this path also must be done in PF's driver.
>
>No, the network core should create that symlink, not the driver, right?
>
>thanks,
>
>greg k-h
Furthermore, the links are already there in sysfs, created by the PCI subsystem.
/sys/class/net/ethX/device links to the PCI device entry for the PF device, which itself has symlinks to each of the VF devices.
This patch just isn't necessary.
-Mitch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists