search for: pci_iov_read_config

...fs) + +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 size); + - int pci_iov_write_config(struct pci_dev *dev, int id, + char *entry, char *buf); +3.2 Usage example + +Following piece of code illustrates the usage of APIs above. + +static char...

...fs) + +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 size); + - int pci_iov_write_config(struct pci_dev *dev, int id, + char *entry, char *buf); +3.2 Usage example + +Following piece of code illustrates the usage of APIs above. + +static char...

...ed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + struct pci_iov *iov = dev->iov; + + BUG_ON(!iov || !iov->notify); + mutex_lock(&iov->mutex); + iov_disable(iov); + mutex_unlock(&iov->mutex); +} +EXPORT_SYMBOL_GPL(pci_iov_disable); + +/** + * pci_iov_read_config - read SR-IOV configurations + * @dev: the PCI device + * @vfn: Virtual Function Number + * @entry: the entry to be read + * @buf: the buffer to be filled + * @size: size of the buffer + * + * Returns 0 on success, or negative on failure. + */ +int pci_iov_read_config(struct pci_dev *dev, int vfn,...

...ed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + struct pci_iov *iov = dev->iov; + + BUG_ON(!iov || !iov->notify); + mutex_lock(&iov->mutex); + iov_disable(iov); + mutex_unlock(&iov->mutex); +} +EXPORT_SYMBOL_GPL(pci_iov_disable); + +/** + * pci_iov_read_config - read SR-IOV configurations + * @dev: the PCI device + * @vfn: Virtual Function Number + * @entry: the entry to be read + * @buf: the buffer to be filled + * @size: size of the buffer + * + * Returns 0 on success, or negative on failure. + */ +int pci_iov_read_config(struct pci_dev *dev, int vfn,...

...ed. + */ +void pci_iov_disable(struct pci_dev *dev) +{ + struct pci_iov *iov = dev->iov; + + BUG_ON(!iov || !iov->notify); + mutex_lock(&iov->mutex); + iov_disable(iov); + mutex_unlock(&iov->mutex); +} +EXPORT_SYMBOL_GPL(pci_iov_disable); + +/** + * pci_iov_read_config - read SR-IOV configurations + * @dev: the PCI device + * @vfn: Virtual Function Number + * @entry: the entry to be read + * @buf: the buffer to be filled + * @size: size of the buffer + * + * Returns 0 on success, or negative on failure. + */ +int pci_iov_read_config(struct pci_dev *dev, int vfn,...

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