search for: dev_probe

...*/ + + vfn = event & PCI_IOV_VIRTFN_ID; + + /* read the config that has been written by user */ + err = pci_iov_read_config(dev, vfn, entry, buf, size); + + } else + return -EINVAL; + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err; + + err = pci_iov_register(dev, callback, entries); + ... + + err = pci_iov_enable(dev, nr_virtfn, callback); + + ... + + return err; +} + +static void __devexit de...

...*/ + + vfn = event & PCI_IOV_VIRTFN_ID; + + /* read the config that has been written by user */ + err = pci_iov_read_config(dev, vfn, entry, buf, size); + + } else + return -EINVAL; + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err; + + err = pci_iov_register(dev, callback, entries); + ... + + err = pci_iov_enable(dev, nr_virtfn, callback); + + ... + + return err; +} + +static void __devexit de...

...* adjust hardware resources if needed + * NOTE: arg is the new requested NumVFs + */ + break; + case PCI_IOV_VF_ERR: /* error occurred */ + /* + * error handling + * NOTE: arg is the error code + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err, nvfs; + + ... + + nvfs = pci_iov_max_virtfn(dev); + if (nvfs <= 0) + return -ENODEV; + + err = pci_iov_enable(dev, nvfs, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *de...

...* adjust hardware resources if needed + * NOTE: arg is the new requested NumVFs + */ + break; + case PCI_IOV_VF_ERR: /* error occurred */ + /* + * error handling + * NOTE: arg is the error code + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err, nvfs; + + ... + + nvfs = pci_iov_max_virtfn(dev); + if (nvfs <= 0) + return -ENODEV; + + err = pci_iov_enable(dev, nvfs, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *de...

...* adjust hardware resources if needed + * NOTE: arg is the new requested NumVFs + */ + break; + case PCI_IOV_VF_ERR: /* error occurred */ + /* + * error handling + * NOTE: arg is the error code + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err, nvfs; + + ... + + nvfs = pci_iov_max_virtfn(dev); + if (nvfs <= 0) + return -ENODEV; + + err = pci_iov_enable(dev, nvfs, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *de...

...* parameter of a Virtual Function has been changed, take + * corresponding actions if needed. + */ + break; + case PCI_IOV_VF_GETPARAM: + /* + * return the parameters of a Virtual Function if any. + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err; + + ... + + err = pci_iov_enable(dev, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *dev) +{ + ... + + pci_iov_disable(dev); + + ... +} + +#ifdef CONFIG_PM +/* + * If the dev...

...* parameter of a Virtual Function has been changed, take + * corresponding actions if needed. + */ + break; + case PCI_IOV_VF_GETPARAM: + /* + * return the parameters of a Virtual Function if any. + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err; + + ... + + err = pci_iov_enable(dev, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *dev) +{ + ... + + pci_iov_disable(dev); + + ... +} + +#ifdef CONFIG_PM +/* + * If the dev...

...* parameter of a Virtual Function has been changed, take + * corresponding actions if needed. + */ + break; + case PCI_IOV_VF_GETPARAM: + /* + * return the parameters of a Virtual Function if any. + */ + break; + default: + return -EINVAL; + } + + return err; +} + +static int __devinit dev_probe(struct pci_dev *dev, + const struct pci_device_id *id) +{ + int err; + + ... + + err = pci_iov_enable(dev, callback); + if (err) + return err; + + ... +} + +static void __devexit dev_remove(struct pci_dev *dev) +{ + ... + + pci_iov_disable(dev); + + ... +} + +#ifdef CONFIG_PM +/* + * If the dev...

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