search for: dev_id_table

...pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, numvfs); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV Physical Function driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.5.6.4

...pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, numvfs); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV Physical Function driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.5.6.4

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.4.2.1

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.4.2.1

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.4.2.1

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.5.6.4

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.5.6.4

...struct pci_dev *dev, pm_message_t state) +{ + ... + + pci_iov_disable(dev); + + ... +} + +static int dev_resume(struct pci_dev *dev) +{ + ... + + pci_iov_enable(dev, nvfs, callback); + + ... +} +#endif + +static struct pci_driver dev_driver = { + .name = "SR-IOV PF driver", + .id_table = dev_id_table, + .probe = dev_probe, + .remove = __devexit_p(dev_remove), +#ifdef CONFIG_PM + .suspend = dev_suspend, + .resume = dev_resume, +#endif +}; -- 1.5.6.4

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. [PATCH 1/8 v4] PCI: define PCI resource names in a 'enum' [PATCH 2/8 v4] PCI: export __pci_read_base

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. [PATCH 1/8 v4] PCI: define PCI resource names in a 'enum' [PATCH 2/8 v4] PCI: export __pci_read_base

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. Major changes between v4 -> v5: 1, remove interfaces for PF driver to create sysfs entries (Matthew

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. Major changes between v4 -> v5: 1, remove interfaces for PF driver to create sysfs entries (Matthew

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. Changes from v5 to v6: 1, update ABI document to include SR-IOV sysfs entries (Greg KH) 2, fix two coding

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. Changes from v5 to v6: 1, update ABI document to include SR-IOV sysfs entries (Greg KH) 2, fix two coding

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. Changes from v5 to v6: 1, update ABI document to include SR-IOV sysfs entries (Greg KH) 2, fix two coding