search for: pci_iov_bus_range

...| 3 +++ 3 files changed, 32 insertions(+), 0 deletions(-) diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c index a2b2de9..17ada58 100644 --- a/drivers/pci/iov.c +++ b/drivers/pci/iov.c @@ -600,6 +600,30 @@ void pci_iov_remove_sysfs(struct pci_dev *dev) kfree(iov->ve); } +/** + * pci_iov_bus_range - find bus range used by SR-IOV capability + * @bus: the PCI bus + * + * Returns max number of buses (exclude current one) used by Virtual + * Functions. + */ +int pci_iov_bus_range(struct pci_bus *bus) +{ + int max = 0; + u8 busnr, devfn; + struct pci_dev *dev; + + list_for...

...up_read(&pci_bus_sem); + + for (i = 1; i <= dev->iov->maxbus; i++) { + bus = find_bus(dev, dev->bus->number + i); + if (!bus) + break; + pci_remove_bus(bus); + kfree(bus); + } +done: + mutex_unlock(&iov_lock); + + kfree(dev->iov); + dev->iov = NULL; +} + +/** + * pci_iov_bus_range - find bus requirement from SR-IOV capability + * @bus: the PCI bus + * + * Returns max number of buses (exclude current bus) used by all Virtual + * Functions on a bus. + */ +int pci_iov_bus_range(struct pci_bus *bus) +{ + int i; + int max = 0; + struct pci_dev *dev; + struct pci_bus *child; + + d...

...up_read(&pci_bus_sem); + + for (i = 1; i <= dev->iov->maxbus; i++) { + bus = find_bus(dev, dev->bus->number + i); + if (!bus) + break; + pci_remove_bus(bus); + kfree(bus); + } +done: + mutex_unlock(&iov_lock); + + kfree(dev->iov); + dev->iov = NULL; +} + +/** + * pci_iov_bus_range - find bus requirement from SR-IOV capability + * @bus: the PCI bus + * + * Returns max number of buses (exclude current bus) used by all Virtual + * Functions on a bus. + */ +int pci_iov_bus_range(struct pci_bus *bus) +{ + int i; + int max = 0; + struct pci_dev *dev; + struct pci_bus *child; + + d...

...up_read(&pci_bus_sem); + + for (i = 1; i <= dev->iov->maxbus; i++) { + bus = find_bus(dev, dev->bus->number + i); + if (!bus) + break; + pci_remove_bus(bus); + kfree(bus); + } +done: + mutex_unlock(&iov_lock); + + kfree(dev->iov); + dev->iov = NULL; +} + +/** + * pci_iov_bus_range - find bus requirement from SR-IOV capability + * @bus: the PCI bus + * + * Returns max number of buses (exclude current bus) used by all Virtual + * Functions on a bus. + */ +int pci_iov_bus_range(struct pci_bus *bus) +{ + int i; + int max = 0; + struct pci_dev *dev; + struct pci_bus *child; + + d...

...* Look for them as well. + */ + if (jailhouse_paravirt() && nr_devs == 0) { + for (fn = 1; fn < 8; fn++) { + dev = pci_scan_single_device(bus, devfn + fn); + if (dev) + dev->multifunction = 1; + } + } + } /* Reserve buses for SR-IOV capability */ used_buses = pci_iov_bus_range(bus); -- 2.13.6

...* Look for them as well. + */ + if (jailhouse_paravirt() && nr_devs == 0) { + for (fn = 1; fn < 8; fn++) { + dev = pci_scan_single_device(bus, devfn + fn); + if (dev) + dev->multifunction = 1; + } + } + } /* Reserve buses for SR-IOV capability */ used_buses = pci_iov_bus_range(bus); -- 2.13.6

...* Look for them as well. + */ + if (jailhouse_paravirt() && nr_devs == 0) { + for (fn = 1; fn < 8; fn++) { + dev = pci_scan_single_device(bus, devfn + fn); + if (dev) + dev->multifunction = 1; + } + } + } /* Reserve buses for SR-IOV capability */ used_buses = pci_iov_bus_range(bus); -- 2.13.6

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

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

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

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -