Displaying 20 results from an estimated 300 matches similar to: "[Virtio-for-kvm] [PATCH 3/7] userspace virtio"
2009 Oct 27
0
[PATCH 1/4] Add 'raid' interface class
This patch adds a 'raid' interface class. It is basically a clone
of the existing 'scsi' interface, only allowing up to 128 disks.
Signed-off-by: Hannes Reinecke <hare at suse.de>
---
hw/pc.c | 5 +++++
hw/pci-hotplug.c | 1 +
hw/scsi-disk.c | 17 +++++++++++++++++
hw/scsi-disk.h | 20 +++++++++++++++++++-
qemu-config.c | 2 +-
sysemu.h
2009 Oct 27
0
[PATCH 1/4] Add 'raid' interface class
This patch adds a 'raid' interface class. It is basically a clone
of the existing 'scsi' interface, only allowing up to 128 disks.
Signed-off-by: Hannes Reinecke <hare at suse.de>
---
hw/pc.c | 5 +++++
hw/pci-hotplug.c | 1 +
hw/scsi-disk.c | 17 +++++++++++++++++
hw/scsi-disk.h | 20 +++++++++++++++++++-
qemu-config.c | 2 +-
sysemu.h
2008 Jan 08
1
[PATCH] QEMU KVM balloon support
Add QEMU support for the KVM balloon driver.
Memory hinting is performed via madvise().
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Index: kvm-userspace/libkvm/libkvm.c
===================================================================
--- kvm-userspace.orig/libkvm/libkvm.c
+++ kvm-userspace/libkvm/libkvm.c
@@ -886,6 +886,17 @@ int kvm_is_ready_for_interrupt_injection
return
2008 Jan 08
1
[PATCH] QEMU KVM balloon support
Add QEMU support for the KVM balloon driver.
Memory hinting is performed via madvise().
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Index: kvm-userspace/libkvm/libkvm.c
===================================================================
--- kvm-userspace.orig/libkvm/libkvm.c
+++ kvm-userspace/libkvm/libkvm.c
@@ -886,6 +886,17 @@ int kvm_is_ready_for_interrupt_injection
return
2007 Dec 21
0
[Virtio-for-kvm] [PATCH 2/7] userspace virtio
From 83e942e0c7634121243478fa2f4e3459b33d4a67 Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Wed, 19 Dec 2007 23:43:24 +0200
Subject: [PATCH] virtio network device
This patch implements the backend support for the virtio network
device. The
device is optimized for virtualized environments by limiting the number of
guest=>host transitions per-packet. In the best
2007 Dec 21
0
[Virtio-for-kvm] [PATCH 2/7] userspace virtio
From 83e942e0c7634121243478fa2f4e3459b33d4a67 Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Wed, 19 Dec 2007 23:43:24 +0200
Subject: [PATCH] virtio network device
This patch implements the backend support for the virtio network
device. The
device is optimized for virtualized environments by limiting the number of
guest=>host transitions per-packet. In the best
2009 May 11
0
[PATCH 1/2] qemu-kvm: add MSI-X support
This adds (incomplete) MSI-X support to virtio net device.
Missing is save/load support, and command-line flag to
control the feature.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Makefile.target | 2 +-
hw/msix.c | 362 +++++++++++++++++++++++++++++++++++++++++++++++++++
hw/msix.h | 33 +++++
hw/pci.c | 35 ++++--
hw/pci.h
2009 May 11
0
[PATCH 1/2] qemu-kvm: add MSI-X support
This adds (incomplete) MSI-X support to virtio net device.
Missing is save/load support, and command-line flag to
control the feature.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Makefile.target | 2 +-
hw/msix.c | 362 +++++++++++++++++++++++++++++++++++++++++++++++++++
hw/msix.h | 33 +++++
hw/pci.c | 35 ++++--
hw/pci.h
2009 May 20
0
[PATCHv2-RFC 1/2] qemu-kvm: add MSI-X support
This adds MSI-X support infrastructure and uses that to enable MSI-X
support in virtio net device. Also add a global option to disable MSI-X.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Makefile.target | 2 +-
hw/device-assignment.c | 2 +
hw/msix.c | 447 ++++++++++++++++++++++++++++++++++++++++++++++++
hw/msix.h | 38 ++++
hw/pci.c
2009 May 20
0
[PATCHv2-RFC 1/2] qemu-kvm: add MSI-X support
This adds MSI-X support infrastructure and uses that to enable MSI-X
support in virtio net device. Also add a global option to disable MSI-X.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Makefile.target | 2 +-
hw/device-assignment.c | 2 +
hw/msix.c | 447 ++++++++++++++++++++++++++++++++++++++++++++++++
hw/msix.h | 38 ++++
hw/pci.c
2007 Dec 21
0
[Virtio-for-kvm] [PATCH 1/7] userspace virtio
From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Wed, 19 Dec 2007 23:07:16 +0200
Subject: [PATCH] [PATCH 1/3] virtio infrastructure
This patch implements the basic infrastructure for virtio devices. These
devices are exposed to the guest as real PCI devices. The PCI vendor/device
IDs have been donated by Qumranet and the
2007 Dec 21
0
[Virtio-for-kvm] [PATCH 1/7] userspace virtio
From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Wed, 19 Dec 2007 23:07:16 +0200
Subject: [PATCH] [PATCH 1/3] virtio infrastructure
This patch implements the basic infrastructure for virtio devices. These
devices are exposed to the guest as real PCI devices. The PCI vendor/device
IDs have been donated by Qumranet and the
2014 Nov 26
1
[PATCH RFC v3 11/12] virtio-net/virtio-blk: enable virtio 1.0
virtio-net (non-vhost) and virtio-blk have everything in place to support
virtio 1.0: let's enable the feature bit for them.
Note that VIRTIO_F_VERSION_1 is technically a transport feature; once
every device is ready for virtio 1.0, we can move this setting this
feature bit out of the individual devices.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
2014 Nov 26
0
[PATCH RFC v3 11/12] virtio-net/virtio-blk: enable virtio 1.0
On Wed, Nov 26, 2014 at 06:28:42PM +0100, Cornelia Huck wrote:
> virtio-net (non-vhost) and virtio-blk have everything in place to support
> virtio 1.0: let's enable the feature bit for them.
Hmm I doubt that.
At least not without more patches.
For block, scsi, wce and config-wce must be off, and
it must support ANY_LAYOUT (which might be a bit more code).
For net, header size is
2014 Dec 11
0
[PATCH RFC v6 19/20] virtio-blk: revision specific feature bits
Wire up virtio-blk to provide different feature bit sets depending
on whether legacy or v1.0 has been requested.
Note that VERSION_1 is still disabled due to missing ANY_LAYOUT support.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
hw/block/virtio-blk.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
2014 Nov 26
1
[PATCH RFC v3 11/12] virtio-net/virtio-blk: enable virtio 1.0
virtio-net (non-vhost) and virtio-blk have everything in place to support
virtio 1.0: let's enable the feature bit for them.
Note that VIRTIO_F_VERSION_1 is technically a transport feature; once
every device is ready for virtio 1.0, we can move this setting this
feature bit out of the individual devices.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
2014 Dec 11
0
[PATCH RFC v6 19/20] virtio-blk: revision specific feature bits
Wire up virtio-blk to provide different feature bit sets depending
on whether legacy or v1.0 has been requested.
Note that VERSION_1 is still disabled due to missing ANY_LAYOUT support.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
hw/block/virtio-blk.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
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
2014 Dec 28
2
[PATCH RFC v6 19/20] virtio-blk: revision specific feature bits
On Thu, Dec 11, 2014 at 02:25:21PM +0100, Cornelia Huck wrote:
> Wire up virtio-blk to provide different feature bit sets depending
> on whether legacy or v1.0 has been requested.
>
> Note that VERSION_1 is still disabled due to missing ANY_LAYOUT support.
>
> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
So we need some way for devices to tell transports