23 Jan, 2015
1 commit
-
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with fist revision of the OASIS spec)
and drives the device accordingly.3. New version uses direct addressing (64 bit address split into two
low/high register) instead of the guest page size based one,
and addresses each part of the queue (descriptors, available, used)
separately.4. The device activity is now explicitly triggered by writing to the
"queue ready" register.5. Whole 64 bit features are properly handled now (both ways).
Signed-off-by: Pawel Moll
Acked-by: Michael S. Tsirkin
Signed-off-by: Rusty Russell
24 Nov, 2011
1 commit
-
Guest features selector spelling mistake.
Cc: Pawel Moll
Cc: Rusty Russell
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Sasha Levin
Signed-off-by: Rusty Russell
02 Nov, 2011
1 commit
-
This patch, based on virtio PCI driver, adds support for memory
mapped (platform) virtio device. This should allow environments
like qemu to use virtio-based block & network devices even on
platforms without PCI support.One can define and register a platform device which resources
will describe memory mapped control registers and "mailbox"
interrupt. Such device can be also instantiated using the Device
Tree node with compatible property equal "virtio,mmio".Cc: Anthony Liguori
Cc: Michael S.Tsirkin
Signed-off-by: Pawel Moll
Signed-off-by: Rusty Russell