Hi, Christian discovered some problems with regard to serialization in the virtio-ccw guest driver. Per-device data structures might contain data obtained by channel programs issued later on, leading to confusing behaviour. We cannot rely on the common I/O layer serialization here. Rather than adding extra serialization, we decided to keep it simple with per-request allocated data structures and retries on busy. These patches have been run in our internal testing without problems for a bit now. Please apply to kvm-next. Christian Borntraeger (1): KVM: s390: Gracefully handle busy conditions on ccw_device_start Cornelia Huck (1): KVM: s390: Dynamic allocation of virtio-ccw I/O data. drivers/s390/kvm/virtio_ccw.c | 291 ++++++++++++++++++++++++++---------------- 1 file changed, 181 insertions(+), 110 deletions(-) -- 1.7.12.4 -- 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
