Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756376Ab0FASre (ORCPT ); Tue, 1 Jun 2010 14:47:34 -0400 Received: from kroah.org ([198.145.64.141]:46924 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756230Ab0FASrd (ORCPT ); Tue, 1 Jun 2010 14:47:33 -0400 Date: Tue, 1 Jun 2010 11:39:20 -0700 From: Greg KH To: Frank Pan Cc: Andrew Morton , Jesse Barnes , Kenji Kaneshige , Yu Zhao , Chris Wright , Mitch Williams , "Rafael J. Wysocki" , "David S. Miller" , Matt Carlson , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Add a helper function in PCI IOV to get VF device Message-ID: <20100601183920.GB19955@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 823 Lines: 23 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/