search for: numvf

...rivers/pciback/'' +SYSFS_PCIBACK_NEWSLOT = ''new_slot'' +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...

...bj, 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(struct kobject *kobj, + struct attribute *att...

...bj, 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(struct kobject *kobj, + struct attribute *att...

...bj, 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(struct kobject *kobj, + struct attribute *att...

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

...from 0 to initialvfs-1) + +To enable or disable SR-IOV: + - /sys/bus/pci/devices/BB:DD.F/iov/enable + (writing 1/0 means enable/disable VFs, state change will + 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:...

...from 0 to initialvfs-1) + +To enable or disable SR-IOV: + - /sys/bus/pci/devices/BB:DD.F/iov/enable + (writing 1/0 means enable/disable VFs, state change will + 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:...

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

...int. + + +2. User Guide + +2.1 How can I manage SR-IOV + +SR-IOV can be managed by reading or writing /sys/bus/pci/devices/.../iov. +Legal operations on this file include: + - Read: will get number of available VFs and a list of them. + - Write: bb:dd.f={1|0} will enable or disable a VF. + - Write: NumVFs=N will change number of available VFs. + +2.2 How can I use Virtual Functions + +Virtual Functions can be treated as hot-plugged PCI devices in the kernel, +so they should be able to work in the same way as real PCI devices. +NOTE: Virtual Function device driver must be loaded to make it work. + +...

...int. + + +2. User Guide + +2.1 How can I manage SR-IOV + +SR-IOV can be managed by reading or writing /sys/bus/pci/devices/.../iov. +Legal operations on this file include: + - Read: will get number of available VFs and a list of them. + - Write: bb:dd.f={1|0} will enable or disable a VF. + - Write: NumVFs=N will change number of available VFs. + +2.2 How can I use Virtual Functions + +Virtual Functions can be treated as hot-plugged PCI devices in the kernel, +so they should be able to work in the same way as real PCI devices. +NOTE: Virtual Function device driver must be loaded to make it work. + +...

...int. + + +2. User Guide + +2.1 How can I manage SR-IOV + +SR-IOV can be managed by reading or writing /sys/bus/pci/devices/.../iov. +Legal operations on this file include: + - Read: will get number of available VFs and a list of them. + - Write: bb:dd.f={1|0} will enable or disable a VF. + - Write: NumVFs=N will change number of available VFs. + +2.2 How can I use Virtual Functions + +Virtual Functions can be treated as hot-plugged PCI devices in the kernel, +so they should be able to work in the same way as real PCI devices. +NOTE: Virtual Function device driver must be loaded to make it work. + +...

...39;\n') + break; + + if (j >= VF_PARAM_LEN - 1) + return -E2BIG; + + buf[j++] = str[i]; + } + + buf[j] = '\0'; + + return j ? i : 0; +} + +static int parse_line(char *str, u16 *bdf, u16 *nvfs, char **ptr) +{ + u8 b, d, f, val; + int err; + char *p; + + + err = sscanf(str, "NumVFs=%hu", nvfs); + if (err == 1) + return 1; + + err = sscanf(str, "%2hhx:%2hhx.%1hhu=%1hhu", &b, &d, &f, &val); + if (err != 4) + return -EINVAL; + + *bdf = (b << 8) + PCI_DEVFN(d, f); + if (!val) + return 2; + + for (p = str + 9; *p != '\0'; p++) + if...

...39;\n') + break; + + if (j >= VF_PARAM_LEN - 1) + return -E2BIG; + + buf[j++] = str[i]; + } + + buf[j] = '\0'; + + return j ? i : 0; +} + +static int parse_line(char *str, u16 *bdf, u16 *nvfs, char **ptr) +{ + u8 b, d, f, val; + int err; + char *p; + + + err = sscanf(str, "NumVFs=%hu", nvfs); + if (err == 1) + return 1; + + err = sscanf(str, "%2hhx:%2hhx.%1hhu=%1hhu", &b, &d, &f, &val); + if (err != 4) + return -EINVAL; + + *bdf = (b << 8) + PCI_DEVFN(d, f); + if (!val) + return 2; + + for (p = str + 9; *p != '\0'; p++) + if...

...39;\n') + break; + + if (j >= VF_PARAM_LEN - 1) + return -E2BIG; + + buf[j++] = str[i]; + } + + buf[j] = '\0'; + + return j ? i : 0; +} + +static int parse_line(char *str, u16 *bdf, u16 *nvfs, char **ptr) +{ + u8 b, d, f, val; + int err; + char *p; + + + err = sscanf(str, "NumVFs=%hu", nvfs); + if (err == 1) + return 1; + + err = sscanf(str, "%2hhx:%2hhx.%1hhu=%1hhu", &b, &d, &f, &val); + if (err != 4) + return -EINVAL; + + *bdf = (b << 8) + PCI_DEVFN(d, f); + if (!val) + return 2; + + for (p = str + 9; *p != '\0'; p++) + if...