search for: totalvf

...\ + struct pci_iov *iov = container_of(kobj, struct pci_iov, kobj); \ + \ + return sprintf(buf, "%d\n", iov->field); \ +} + +iov_config_attr(is_enabled); +iov_config_attr(totalvfs); +iov_config_attr(initialvfs); +iov_config_attr(numvfs); + +struct vf_entry { + int vfn; + struct kobject kobj; + struct pci_iov *iov; + struct iov_attr *attr; + char name[VF_NAME_LEN]; + char (*param)[PCI_IOV_PARAM_LEN]; +}; + +static ssize_t iov_attr_show(str...

...\ + struct pci_iov *iov = container_of(kobj, struct pci_iov, kobj); \ + \ + return sprintf(buf, "%d\n", iov->field); \ +} + +iov_config_attr(is_enabled); +iov_config_attr(totalvfs); +iov_config_attr(initialvfs); +iov_config_attr(numvfs); + +struct vf_entry { + int vfn; + struct kobject kobj; + struct pci_iov *iov; + struct iov_attr *attr; + char name[VF_NAME_LEN]; + char (*param)[PCI_IOV_PARAM_LEN]; +}; + +static ssize_t iov_attr_show(str...

...\ + struct pci_iov *iov = container_of(kobj, struct pci_iov, kobj); \ + \ + return sprintf(buf, "%d\n", iov->field); \ +} + +iov_config_attr(is_enabled); +iov_config_attr(totalvfs); +iov_config_attr(initialvfs); +iov_config_attr(numvfs); + +struct vf_entry { + int vfn; + struct kobject kobj; + struct pci_iov *iov; + struct iov_attr *attr; + char name[VF_NAME_LEN]; + char (*param)[PCI_IOV_PARAM_LEN]; +}; + +static ssize_t iov_attr_show(str...

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

...'' +SYSFS_PCIBACK_REMOVESLOT = ''remove_slot'' +SYSFS_PCI_IOV_ENTRY = ''/iov/'' +SYSFS_PCI_IOV_RID = ''rid'' +SYSFS_PCI_IOV_ENABLE = ''enable'' +SYSFS_PCI_IOV_NUMVFS = ''numvfs'' +SYSFS_PCI_IOV_TOTAL = ''totalvfs'' +SYSFS_PCI_IOV_INITIAL = ''initialvfs'' LSPCI_CMD = ''lspci'' @@ -330,6 +338,173 @@ result = result + [dev_list] return result + +def pci_dev_name(dev): + match = re.match(r"((?P<d>[0-9a-fA-F]{1,4})[:,])?" + \ +...

...t pci_iov_bus_range(struct pci_bus *bus) +{ + int max = 0; + u8 busnr, devfn; + struct pci_dev *dev; + + list_for_each_entry(dev, &bus->devices, bus_list) { + if (!dev->iov) + continue; + vf_rid(dev, dev->iov->totalvfs - 1, &busnr, &devfn); + if (busnr > max) + max = busnr; + } + + return max ? max - bus->number : 0; +} + int pci_iov_resource_align(struct pci_dev *dev, int resno) { if (resno < PCI_IOV_RESOURCES || resno > PCI_IOV_RESOU...

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

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

...l + notify PF driver) + +To change number of Virtual Functions: + - /sys/bus/pci/devices/BB:DD.F/iov/numvfs + (writing positive integer to this file will change NumVFs) + +The total and initial number of VFs can get from: + - /sys/bus/pci/devices/BB:DD.F/iov/totalvfs + - /sys/bus/pci/devices/BB:DD.F/iov/initialvfs + +The identifier of a VF that belongs to this PF can get from: + - /sys/bus/pci/devices/BB:DD.F/iov/N/rid + (for all class of devices) + +For network device, there are: + - /sys/bus/pci/devices/BB:DD.F/iov/N/mac +...

...l + notify PF driver) + +To change number of Virtual Functions: + - /sys/bus/pci/devices/BB:DD.F/iov/numvfs + (writing positive integer to this file will change NumVFs) + +The total and initial number of VFs can get from: + - /sys/bus/pci/devices/BB:DD.F/iov/totalvfs + - /sys/bus/pci/devices/BB:DD.F/iov/initialvfs + +The identifier of a VF that belongs to this PF can get from: + - /sys/bus/pci/devices/BB:DD.F/iov/N/rid + (for all class of devices) + +For network device, there are: + - /sys/bus/pci/devices/BB:DD.F/iov/N/mac +...