virtio drivers implementation details
Hi,
I'm trying to develop a custom virtio driver for myself. Can I ask here virtio driver implementation details? I've tried the kvm and qemu irc channel, but had no luck.
This is the link to the presentation:
http://www.slideshare.net/zenixls2/052-virtio-introduction-17191942
I'm trying to make a custom virtio driver that mostly interacts with memory. I've came upon a presentation which shows which files need to be edited on qemu and kvm in order to add a new virtio driver.
One of the files in qemu is include/hw/pci/pci.h,
but that was an example specific to virtio pci.
virtio-mmio is better mapped on my situation, but I can't seem to find a similar header for it. In fact I can't find anything related to virtio mmio through out the header files
Quoted 10 lines · On Tue, Dec 02, 2014 at 01:26:10PM +0200, Vasile Catalin-B50542 wrote:
I'm trying to make a custom virtio driver that mostly interacts with memory. I've came upon a presentation which shows which files need to be edited on qemu
and kvm in order to add a new virtio driver.
One of the files in qemu isinclude/hw/pci/pci.h,
but that was an example specific to virtio pci.
virtio-mmio is better mapped on my situation, but I can't seem to find a similar header for it.
In fact I can't find anything related to virtio mmio through out the header files
If you are adding a new device type (e.g. printer device) then the code should not depend on the transport (PCI, MMIO, CCW, etc).
Can you explain what type of device you are trying to implement?
Stefan