search for: request_resourc

...to prevent any legacy drivers + * from wasting time probing for their hardware. This is a fairly + * brute-force approach to disabling all non-virtual drivers. + * + * Note that this must be called very early to have any effect. + */ +int paravirt_disable_iospace(void) +{ + int ret = 0; + + ret = request_resource(&ioport_resource, &reserve_ioports); + if (ret == 0) + ret = request_resource(&iomem_resource, &reserve_iomem); + + return ret; +} + struct paravirt_ops paravirt_ops = { .name = "bare hardware", diff -r 83c67f9402b5 arch/i386/xen/setup.c --- a/arch/i386/xen/setup.c...

...h/i386/kernel/paravirt.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) =================================================================== --- a/arch/i386/kernel/paravirt.c +++ b/arch/i386/kernel/paravirt.c @@ -254,8 +254,11 @@ int paravirt_disable_iospace(void) int ret; ret = request_resource(&ioport_resource, &reserve_ioports); - if (ret == 0) + if (ret == 0) { ret = request_resource(&iomem_resource, &reserve_iomem); + if (ret) + release_resource(&reserve_ioports); + } return ret; }

...legacy IO space to prevent any legacy drivers - * from wasting time probing for their hardware. This is a fairly - * brute-force approach to disabling all non-virtual drivers. - * - * Note that this must be called very early to have any effect. - */ -int paravirt_disable_iospace(void) -{ - return request_resource(&ioport_resource, &reserve_ioports); -} - static DEFINE_PER_CPU(enum paravirt_lazy_mode, paravirt_lazy_mode) = PARAVIRT_LAZY_NONE; static inline void enter_lazy(enum paravirt_lazy_mode mode) -- 2.12.0

Hi folks, With this series, the bulk of the work of pvops64 is done. Here, I integrate most of the paravirt.c and paravirt.h files, making them applicable to both architectures. CONFIG_PARAVIRT is _not_ present yet. Basically, this code is missing page table integration (patches currently being worked on by Jeremy). Enjoy

Hi folks, With this series, the bulk of the work of pvops64 is done. Here, I integrate most of the paravirt.c and paravirt.h files, making them applicable to both architectures. CONFIG_PARAVIRT is _not_ present yet. Basically, this code is missing page table integration (patches currently being worked on by Jeremy). Enjoy

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

...parent) + continue; + new->resource[i].name = pci_name(new); + new->resource[i].flags = res->flags; + size = resource_size(res) / dev->iov->total; + new->resource[i].start = res->start + size * id; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + return pci_bus_add_device(new); +} + +static int enable_virtfn(struct hotplug_sl...

...parent) + continue; + new->resource[i].name = pci_name(new); + new->resource[i].flags = res->flags; + size = resource_size(res) / dev->iov->total; + new->resource[i].start = res->start + size * id; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + return pci_bus_add_device(new); +} + +static int enable_virtfn(struct hotplug_sl...

...parent) + continue; + new->resource[i].name = pci_name(new); + new->resource[i].flags = res->flags; + size = resource_size(res) / dev->iov->total; + new->resource[i].start = res->start + size * id; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + return pci_bus_add_device(new); +} + +static int enable_virtfn(struct hotplug_sl...

...ew->resource[i].flags = res->flags; + size = (res->end - res->start + 1) / dev->iov->totalvfs; + new->resource[i].start = res->start + size * vfn; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + pci_bus_add_device(new); + retu...

...new->resource[i].flags = res->flags; + size = resource_size(res) / dev->iov->totalvfs; + new->resource[i].start = res->start + size * vfn; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + return pci_bus_add_device(new); +} +...

...new->resource[i].flags = res->flags; + size = resource_size(res) / dev->iov->totalvfs; + new->resource[i].start = res->start + size * vfn; + new->resource[i].end = new->resource[i].start + size - 1; + rc = request_resource(res, &new->resource[i]); + BUG_ON(rc); + } + + new->subsystem_vendor = dev->subsystem_vendor; + pci_read_config_word(new, PCI_SUBSYSTEM_ID, &new->subsystem_device); + + pci_device_add(new, bus); + return pci_bus_add_device(new); +} +...

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