Displaying 4 results from an estimated 4 matches similar to: "[RFC] kvm tools: Implement multiple VQ for virtio-net"
2011 Nov 15
2
[RFC] kvm tools: Add support for virtio-mmio
This patch adds support for the new virtio-mmio transport layer added in
3.2-rc1.
The purpose of this new layer is to allow virtio to work on systems which
don't necessarily support PCI, such as embedded systems.
To apply the patch on top of the KVM tools tree, you must first pull Linus'
tree on top. Also, CONFIG_VIRTIO_MMIO=y should be set in the guest kernel.
This is an early RFC,
2011 Nov 15
2
[RFC] kvm tools: Add support for virtio-mmio
This patch adds support for the new virtio-mmio transport layer added in
3.2-rc1.
The purpose of this new layer is to allow virtio to work on systems which
don't necessarily support PCI, such as embedded systems.
To apply the patch on top of the KVM tools tree, you must first pull Linus'
tree on top. Also, CONFIG_VIRTIO_MMIO=y should be set in the guest kernel.
This is an early RFC,
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
This is a first go at adding support for the modern (based on the 1.0 virtio
spec) virtio-pci implementation.
kvmtool makes it simple to add additional transports such as this because of
it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and
virtio-mmio) transport layer, and still allow users to choose to use either
the legacy or the modern implementations (but setting
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
This is a first go at adding support for the modern (based on the 1.0 virtio
spec) virtio-pci implementation.
kvmtool makes it simple to add additional transports such as this because of
it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and
virtio-mmio) transport layer, and still allow users to choose to use either
the legacy or the modern implementations (but setting