search for: pci_iov_disable

...unction device driver needs to call: + void pci_iov_unregister(struct pci_dev *dev) + +To enable SR-IOV, Physical Function device driver needs to call: + int pci_iov_enable(struct pci_dev *dev, int numvfs) + +To disable SR-IOV, Physical Function device driver needs to call: + void pci_iov_disable(struct pci_dev *dev) + +Note: above two functions sleeps 1 second waiting on hardware transaction +completion according to SR-IOV specification. + +To read or write VFs configuration: + - int pci_iov_read_config(struct pci_dev *dev, int id, + char *entry, char *buf, int...

...unction device driver needs to call: + void pci_iov_unregister(struct pci_dev *dev) + +To enable SR-IOV, Physical Function device driver needs to call: + int pci_iov_enable(struct pci_dev *dev, int numvfs) + +To disable SR-IOV, Physical Function device driver needs to call: + void pci_iov_disable(struct pci_dev *dev) + +Note: above two functions sleeps 1 second waiting on hardware transaction +completion according to SR-IOV specification. + +To read or write VFs configuration: + - int pci_iov_read_config(struct pci_dev *dev, int id, + char *entry, char *buf, int...

...TRL, ctrl); + ssleep(1); + + return rc; +} + +static int iov_disable(struct pci_iov *iov) +{ + int i; + u16 ctrl; + + if (!iov->notify) + return -ENODEV; + + if (!iov->is_enabled) + return 0; + + iov->notify(iov->dev, PCI_IOV_DISABLE); + for (i = 0; i < iov->numvfs; i++) + vf_remove(iov->dev, i); + + pci_read_config_word(iov->dev, iov->cap + PCI_IOV_CTRL, &ctrl); + ctrl &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + pci_write_config_word(iov->dev, iov->cap + PCI_I...

...s to call: + int pci_iov_enable(struct pci_dev *dev, int nvfs, + int (*cb)(struct pci_dev *, int, int)) +NOTE: this function sleeps 2 seconds waiting on hardware transaction +completion according to SR-IOV specification. + +To disable SR-IOV, Physical Function device driver needs to call: + void pci_iov_disable(struct pci_dev *dev) +NOTE: this function sleeps 1 second waiting on hardware transaction +completion according to SR-IOV specification. + +Following function can be used to query maximum number of Virtual Functions +that a Physical Function can support: + int pci_iov_max_virtfn(struct pci_dev *dev...

...s to call: + int pci_iov_enable(struct pci_dev *dev, int nvfs, + int (*cb)(struct pci_dev *, int, int)) +NOTE: this function sleeps 2 seconds waiting on hardware transaction +completion according to SR-IOV specification. + +To disable SR-IOV, Physical Function device driver needs to call: + void pci_iov_disable(struct pci_dev *dev) +NOTE: this function sleeps 1 second waiting on hardware transaction +completion according to SR-IOV specification. + +Following function can be used to query maximum number of Virtual Functions +that a Physical Function can support: + int pci_iov_max_virtfn(struct pci_dev *dev...

...s to call: + int pci_iov_enable(struct pci_dev *dev, int nvfs, + int (*cb)(struct pci_dev *, int, int)) +NOTE: this function sleeps 2 seconds waiting on hardware transaction +completion according to SR-IOV specification. + +To disable SR-IOV, Physical Function device driver needs to call: + void pci_iov_disable(struct pci_dev *dev) +NOTE: this function sleeps 1 second waiting on hardware transaction +completion according to SR-IOV specification. + +Following function can be used to query maximum number of Virtual Functions +that a Physical Function can support: + int pci_iov_max_virtfn(struct pci_dev *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

...le(&dev->dev.kobj, &dev_attr_iov.attr); + if (err) + goto failed2; + + dev_info(&dev->dev, "IOV is enabled\n"); + return 0; + +failed2: + iov_set_vfe(dev, 0); +failed1: + kfree(iov); + dev->iov = NULL; + + return err; +} +EXPORT_SYMBOL_GPL(pci_iov_enable); + +/** + * pci_iov_disable - disable device's SR-IOV capability + * @dev: PCI device + * + * Should be called upon Physical Function removal, or power state + * change. All previous allocated Virtual Functions are reclaimed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + int i; + struct pci_iov *iov = dev->iov;...

...le(&dev->dev.kobj, &dev_attr_iov.attr); + if (err) + goto failed2; + + dev_info(&dev->dev, "IOV is enabled\n"); + return 0; + +failed2: + iov_set_vfe(dev, 0); +failed1: + kfree(iov); + dev->iov = NULL; + + return err; +} +EXPORT_SYMBOL_GPL(pci_iov_enable); + +/** + * pci_iov_disable - disable device's SR-IOV capability + * @dev: PCI device + * + * Should be called upon Physical Function removal, or power state + * change. All previous allocated Virtual Functions are reclaimed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + int i; + struct pci_iov *iov = dev->iov;...

...le(&dev->dev.kobj, &dev_attr_iov.attr); + if (err) + goto failed2; + + dev_info(&dev->dev, "IOV is enabled\n"); + return 0; + +failed2: + iov_set_vfe(dev, 0); +failed1: + kfree(iov); + dev->iov = NULL; + + return err; +} +EXPORT_SYMBOL_GPL(pci_iov_enable); + +/** + * pci_iov_disable - disable device's SR-IOV capability + * @dev: PCI device + * + * Should be called upon Physical Function removal, or power state + * change. All previous allocated Virtual Functions are reclaimed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + int i; + struct pci_iov *iov = dev->iov;...

...TRL, ctrl); + ssleep(1); + + return rc; +} + +static int iov_disable(struct pci_iov *iov) +{ + int i; + u16 ctrl; + + if (!iov->notify) + return -ENODEV; + + if (!iov->is_enabled) + return 0; + + iov->notify(iov->dev, PCI_IOV_DISABLE); + for (i = 0; i < iov->numvfs; i++) + vf_remove(iov->dev, i); + + pci_read_config_word(iov->dev, iov->cap + PCI_IOV_CTRL, &ctrl); + ctrl &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + pci_write_config_word(iov->dev, iov->cap + PCI_I...

...TRL, ctrl); + ssleep(1); + + return rc; +} + +static int iov_disable(struct pci_iov *iov) +{ + int i; + u16 ctrl; + + if (!iov->notify) + return -ENODEV; + + if (!iov->is_enabled) + return 0; + + iov->notify(iov->dev, PCI_IOV_DISABLE); + for (i = 0; i < iov->numvfs; i++) + vf_remove(iov->dev, i); + + pci_read_config_word(iov->dev, iov->cap + PCI_IOV_CTRL, &ctrl); + ctrl &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + pci_write_config_word(iov->dev, iov->cap + PCI_I...

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

...LIST_HEAD(&dev->iov->slot); + + dev->iov->cb = cb; + for (i = 0; i < dev->iov->total; i++) { + rc = add_slot(dev, i); + if (rc) + return rc; + } + + dev_info(&dev->dev, "IOV is enabled\n"); + + return 0; +} +EXPORT_SYMBOL_GPL(pci_iov_enable); + +/** + * pci_iov_disable - disable device's SR-IOV capability + * @dev: the PCI device + * + * Should be called upon Physical Function driver removal, and power + * state change. All previous allocated Virtual Functions are reclaimed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + u16 ctrl; + struct virtfn_slot *...

...LIST_HEAD(&dev->iov->slot); + + dev->iov->cb = cb; + for (i = 0; i < dev->iov->total; i++) { + rc = add_slot(dev, i); + if (rc) + return rc; + } + + dev_info(&dev->dev, "IOV is enabled\n"); + + return 0; +} +EXPORT_SYMBOL_GPL(pci_iov_enable); + +/** + * pci_iov_disable - disable device's SR-IOV capability + * @dev: the PCI device + * + * Should be called upon Physical Function driver removal, and power + * state change. All previous allocated Virtual Functions are reclaimed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + u16 ctrl; + struct virtfn_slot *...