summaryrefslogtreecommitdiffstats
path: root/include/qemu/mmap-alloc.h
diff options
context:
space:
mode:
authorCornelia Huck <cornelia.huck@de.ibm.com>2015-12-02 18:31:57 +0100
committerMichael S. Tsirkin <mst@redhat.com>2015-12-02 19:34:11 +0200
commit11380b36196c483ff5c7f800b0f7af6aa53b5657 (patch)
tree616f8cd145d8c08199f51ba39d9cae715c6d5b9a /include/qemu/mmap-alloc.h
parent6d0b908a628a7086fa855c68b217cc1e2a5c4c19 (diff)
downloadhqemu-11380b36196c483ff5c7f800b0f7af6aa53b5657.zip
hqemu-11380b36196c483ff5c7f800b0f7af6aa53b5657.tar.gz
virtio: handle non-virtio-1-capable backend for ccw
If you run a qemu advertising VERSION_1 with an old kernel where vhost did not yet support VERSION_1, you'll end up with a device that is {modern pci|ccw revision 1} but does not advertise VERSION_1. This is not a sensible configuration and is rejected by the Linux guest drivers. To fix this, add a ->post_plugged() callback invoked after features have been queried that can handle the VERSION_1 bit being withdrawn and change ccw to fall back to revision 0 if VERSION_1 is gone. Note that pci is _not_ fixed; we'll need to rethink the approach for the next release but at least for pci it's not a regression. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'include/qemu/mmap-alloc.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud