search for: ssleep

...n 0; + + iov->notify(iov->dev, iov->numvfs | PCI_IOV_ENABLE); + 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_IOV_CTRL, ctrl); + ssleep(1); + + for (i = 0; i < iov->numvfs; i++) { + rc = vf_add(iov->dev, i); + if (rc) + goto failed; + } + + iov->notify(iov->dev, iov->numvfs | + PCI_IOV_ENABLE | PCI_IOV_POST_EVENT); +...

...n 0; + + iov->notify(iov->dev, iov->numvfs | PCI_IOV_ENABLE); + 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_IOV_CTRL, ctrl); + ssleep(1); + + for (i = 0; i < iov->numvfs; i++) { + rc = vf_add(iov->dev, i); + if (rc) + goto failed; + } + + iov->notify(iov->dev, iov->numvfs | + PCI_IOV_ENABLE | PCI_IOV_POST_EVENT); +...

...n 0; + + iov->notify(iov->dev, iov->numvfs | PCI_IOV_ENABLE); + 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_IOV_CTRL, ctrl); + ssleep(1); + + for (i = 0; i < iov->numvfs; i++) { + rc = vf_add(iov->dev, i); + if (rc) + goto failed; + } + + iov->notify(iov->dev, iov->numvfs | + PCI_IOV_ENABLE | PCI_IOV_POST_EVENT); +...

I want to add a sleep() to a module. It tells me it can't find <time.h>; if I tell it "/usr/include/time.h", it gives me a ton of errors (I *have* put the #include just above where I call sleep, not up at the top). Any clues as to what I'm doing wrong? With kernel /vmlinuz-2.6.18-194.3.1.el5, I just added the line extern unsigned int sleep( unsigned int seconds ); and

...ruct resource *res; + + if (dev->pcie_type != PCI_EXP_TYPE_ENDPOINT) + return -ENODEV; + + pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_IOV); + if (!pos) + return -ENODEV; + + ctrl = pci_ari_fwd_enabled(dev) ? PCI_IOV_CTRL_ARI : 0; + pci_write_config_word(dev, pos + PCI_IOV_CTRL, ctrl); + ssleep(1); + + pci_read_config_word(dev, pos + PCI_IOV_INITIAL_VF, &total); + pci_write_config_word(dev, pos + PCI_IOV_NUM_VF, total); + pci_read_config_word(dev, pos + PCI_IOV_VF_OFFSET, &offset); + pci_read_config_word(dev, pos + PCI_IOV_VF_STRIDE, &stride); + if (!total || !offset || (total...

...ruct resource *res; + + if (dev->pcie_type != PCI_EXP_TYPE_ENDPOINT) + return -ENODEV; + + pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_IOV); + if (!pos) + return -ENODEV; + + ctrl = pci_ari_fwd_enabled(dev) ? PCI_IOV_CTRL_ARI : 0; + pci_write_config_word(dev, pos + PCI_IOV_CTRL, ctrl); + ssleep(1); + + pci_read_config_word(dev, pos + PCI_IOV_INITIAL_VF, &total); + pci_write_config_word(dev, pos + PCI_IOV_NUM_VF, total); + pci_read_config_word(dev, pos + PCI_IOV_VF_OFFSET, &offset); + pci_read_config_word(dev, pos + PCI_IOV_VF_STRIDE, &stride); + if (!total || !offset || (total...

...ruct resource *res; + + if (dev->pcie_type != PCI_EXP_TYPE_ENDPOINT) + return -ENODEV; + + pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_IOV); + if (!pos) + return -ENODEV; + + ctrl = pci_ari_fwd_enabled(dev) ? PCI_IOV_CTRL_ARI : 0; + pci_write_config_word(dev, pos + PCI_IOV_CTRL, ctrl); + ssleep(1); + + pci_read_config_word(dev, pos + PCI_IOV_INITIAL_VF, &total); + pci_write_config_word(dev, pos + PCI_IOV_NUM_VF, total); + pci_read_config_word(dev, pos + PCI_IOV_VF_OFFSET, &offset); + pci_read_config_word(dev, pos + PCI_IOV_VF_STRIDE, &stride); + if (!total || !offset || (total...

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

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. 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

...able) { + reg |= (PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + if (pci_ari_fwd_enabled(pf)) + reg |= PCI_IOV_CTRL_ARI; + else + reg &= ~PCI_IOV_CTRL_ARI; + } else + reg &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + pci_write_config_word(pf, pf->iov->cap + PCI_IOV_CTRL, reg); + + ssleep(1); +} + +static int iov_init(struct pci_dev *pf) +{ + int i; + u16 maxbus; + u32 reg; + int err; + int pos = pf->iov->cap; + + iov_set_vfe(pf, 0); + + if (pf->iov->nr_virtfn == 0) + return 0; + + pci_write_config_word(pf, pos + PCI_IOV_NUM_VF, pf->iov->nr_virtfn); + + pci_read_c...

...able) { + reg |= (PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + if (pci_ari_fwd_enabled(pf)) + reg |= PCI_IOV_CTRL_ARI; + else + reg &= ~PCI_IOV_CTRL_ARI; + } else + reg &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + pci_write_config_word(pf, pf->iov->cap + PCI_IOV_CTRL, reg); + + ssleep(1); +} + +static int iov_init(struct pci_dev *pf) +{ + int i; + u16 maxbus; + u32 reg; + int err; + int pos = pf->iov->cap; + + iov_set_vfe(pf, 0); + + if (pf->iov->nr_virtfn == 0) + return 0; + + pci_write_config_word(pf, pos + PCI_IOV_NUM_VF, pf->iov->nr_virtfn); + + pci_read_c...

...able) { + reg |= (PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + if (pci_ari_fwd_enabled(pf)) + reg |= PCI_IOV_CTRL_ARI; + else + reg &= ~PCI_IOV_CTRL_ARI; + } else + reg &= ~(PCI_IOV_CTRL_VFE | PCI_IOV_CTRL_MSE); + + pci_write_config_word(pf, pf->iov->cap + PCI_IOV_CTRL, reg); + + ssleep(1); +} + +static int iov_init(struct pci_dev *pf) +{ + int i; + u16 maxbus; + u32 reg; + int err; + int pos = pf->iov->cap; + + iov_set_vfe(pf, 0); + + if (pf->iov->nr_virtfn == 0) + return 0; + + pci_write_config_word(pf, pos + PCI_IOV_NUM_VF, pf->iov->nr_virtfn); + + pci_read_c...