[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100601183920.GB19955@kroah.com>
Date: Tue, 1 Jun 2010 11:39:20 -0700
From: Greg KH <greg@...ah.com>
To: 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>,
Mitch Williams <mitch.a.williams@...el.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"David S. Miller" <davem@...emloft.net>,
Matt Carlson <mcarlson@...adcom.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Add a helper function in PCI IOV to get VF device
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
--
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