Hi, There seems to be a bug in the VirtIO guest device driver (tested with 2.6.31.5 kernel). The bug causes frequent & excessive VIRTIO_PCI_ISR reads (causing PIO vm-exits) for a device that is not being used. The setup I’m using includes two VirtIO block devices – vda & vdb. While running heavy IO on vdb I notice a lot of VIRTIO_PCI_ISR port reads for the PIO ports of vda too. For each vdb IO operation passed to the hypervisor by the virtio driver I see: 1. One VIRTIO_PCI_QUEUE_NOTIFY write on vdb 2. One VIRTIO_PCI_ISR read on vdb 3. One VIRTIO_PCI_ISR read on vda (while not explicitly using vda) I think that #3 shouldn't happen and I think it is a bug. On my VM setup, vda’s IO ports start at 0xc400 and vdb's IO ports start at 0xc800. Below are the counts of PIO vm-exits distributed by port number: port count 0xc413 17923 0xc810 17922 0xc813 17923 Is this how this VirtIO block devices supposed to work? The extra ISR reads on vda are ok? Thanks, Saul -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
