As noted in the attached email to the netdev list, we (e1000_devel) will support the API. - Greg Rose -----Original Message----- From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] On Behalf Of Greg KH Sent: Tuesday, December 16, 2008 10:06 PM To: Jike Song Cc: Jesse Barnes; Zhao, Yu; linux-pci@xxxxxxxxxxxxxxx; achiang@xxxxxx; bjorn.helgaas@xxxxxx; grundler@xxxxxxxxxxxxxxxx; mingo@xxxxxxx; matthew@xxxxxx; randy.dunlap@xxxxxxxxxx; rdreier@xxxxxxxxx; horms@xxxxxxxxxxxx; yinghai@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx Subject: Re: [PATCH 0/13 v7] PCI: Linux kernel SR-IOV support On Wed, Dec 17, 2008 at 10:37:54AM +0800, Jike Song wrote: > Jesse Barnes wrote: > > Given a respin of 10-13 I think it's reasonable to merge this into 2.6.29, but > > I'd be much happier about it if we got some driver code along with it, so as > > not to have an unused interface sitting around for who knows how many > > releases. Is that reasonable? Do you know if any of the corresponding PF/VF > > driver bits are ready yet? > > Hi Jesse, > > Yu Zhao has posted a patch set with subject "SR-IOV driver example" > at November 26, which illustrated the usage of SR-IOV API in Intel 82576 VF/PF > drivers;-) Yes, but that driver was soundly rejected by the network driver maintainers, so I wouldn't go around showing that as your primary example of how to use this interface :) The point is valid, I don't think these apis should go into the tree without a driver or some other code using them. Otherwise they make no sense at all to have in-tree. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
--- Begin Message ---
- Subject: Re: [SR-IOV driver example 0/3 resend] introduction
- From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@xxxxxxxxx>
- Date: Tue, 2 Dec 2008 19:12:18 -0800
- Cc: "linux-pci@xxxxxxxxxxxxxxx" <linux-pci@xxxxxxxxxxxxxxx>, "greg@xxxxxxxxx" <greg@xxxxxxxxx>, "matthew@xxxxxx" <matthew@xxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "kvm@xxxxxxxxxxxxxxx" <kvm@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx" <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Rose, Gregory V" <gregory.v.rose@xxxxxxxxx>
- In-reply-to: <20081202092741.GA1859@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <20081121183605.GA7810@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20081202092741.GA1859@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Thread-index: AclU9P1ETlKqA/muTzqMDfhqyjYfvg==
- Thread-topic: [SR-IOV driver example 0/3 resend] introduction
On Tue, Dec 2, 2008 at 1:27 AM, Yu Zhao <yu.zhao@xxxxxxxxx> wrote: > SR-IOV drivers of Intel 82576 NIC are available. There are two parts > of the drivers: Physical Function driver and Virtual Function driver. > The PF driver is based on the IGB driver and is used to control PF to > allocate hardware specific resources and interface with the SR-IOV core. > The VF driver is a new NIC driver that is same as the traditional PCI > device driver. It works in both the host and the guest (Xen and KVM) > environment. > > These two drivers are testing versions and they are *only* intended to > show how to use SR-IOV API. > > Intel 82576 NIC specification can be found at: > http://download.intel.com/design/network/datashts/82576_Datasheet_v2p1.pdf > > [SR-IOV driver example 0/3 resend] introduction > [SR-IOV driver example 1/3 resend] PF driver: hardware specific operations > [SR-IOV driver example 2/3 resend] PF driver: integrate with SR-IOV core > [SR-IOV driver example 3/3 resend] VF driver: an independent PCI NIC driver > -- > First of all, we (e1000-devel) do support the SR-IOV API. With that said, NAK on the driver changes. We were not involved in these changes and are currently working on a version of the drivers that will make them acceptable for kernel inclusion. -- Cheers, Jeff
--- End Message ---
