search for: virtio_net_poll

Displaying 4 results from an estimated 4 matches for "virtio_net_poll".

2007 Dec 21
2
[Virtio-for-kvm] [PATCH 7/7] userspace virtio
...), 35 deletions(-) diff --git a/qemu/hw/pc.h b/qemu/hw/pc.h index 95471f3..5d4c747 100644 --- a/qemu/hw/pc.h +++ b/qemu/hw/pc.h @@ -145,7 +145,7 @@ void isa_ne2000_init(int base, qemu_irq irq, NICInfo *nd); /* virtio-net.c */ void *virtio_net_init(PCIBus *bus, NICInfo *nd, int devfn); - +void virtio_net_poll(void); /* virtio-blk.h */ void *virtio_blk_init(PCIBus *bus, uint16_t vendor, uint16_t device, diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c index f6f1f28..b955a5e 100644 --- a/qemu/hw/virtio-net.c +++ b/qemu/hw/virtio-net.c @@ -60,8 +60,13 @@ typedef struct VirtIONet VirtQueue...
2007 Dec 21
2
[Virtio-for-kvm] [PATCH 7/7] userspace virtio
...), 35 deletions(-) diff --git a/qemu/hw/pc.h b/qemu/hw/pc.h index 95471f3..5d4c747 100644 --- a/qemu/hw/pc.h +++ b/qemu/hw/pc.h @@ -145,7 +145,7 @@ void isa_ne2000_init(int base, qemu_irq irq, NICInfo *nd); /* virtio-net.c */ void *virtio_net_init(PCIBus *bus, NICInfo *nd, int devfn); - +void virtio_net_poll(void); /* virtio-blk.h */ void *virtio_blk_init(PCIBus *bus, uint16_t vendor, uint16_t device, diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c index f6f1f28..b955a5e 100644 --- a/qemu/hw/virtio-net.c +++ b/qemu/hw/virtio-net.c @@ -60,8 +60,13 @@ typedef struct VirtIONet VirtQueue...
2008 Jan 09
4
[PATCH/RFC 0/2] CPU hotplug virtio driver
I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio The first patch is the kernel module, while the second, the userspace pci device. The host boots with the maximum cpus it should ever use, through the -smp parameter. Due to real machine constraints (which qemu copies), i386 does not allow for any addition of cpus after boot, so this is the most general way. I do
2008 Jan 09
4
[PATCH/RFC 0/2] CPU hotplug virtio driver
I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio The first patch is the kernel module, while the second, the userspace pci device. The host boots with the maximum cpus it should ever use, through the -smp parameter. Due to real machine constraints (which qemu copies), i386 does not allow for any addition of cpus after boot, so this is the most general way. I do