aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2014-01-15 02:48:40 +0100
committerKevin O'Connor <kevin@koconnor.net>2014-01-17 12:14:43 -0500
commit5f2d17d35b2339526f3b3d580b279ea78e406a25 (patch)
tree34d76b6376856ab394b0e99d42da06d72340ca31 /scripts
parent296ce2278bae60d844f6c5b96c4889f620b6b4bf (diff)
downloadseabios-hppa-5f2d17d35b2339526f3b3d580b279ea78e406a25.zip
seabios-hppa-5f2d17d35b2339526f3b3d580b279ea78e406a25.tar.gz
seabios-hppa-5f2d17d35b2339526f3b3d580b279ea78e406a25.tar.bz2
init_virtio_scsi(): reset the HBA before freeing its virtio ring
When init_virtio_scsi() finds no SCSI targets connected to the HBA, it frees the virtio ring. Other code in SeaBIOS proceeds to overwrite the area. However, the ring is in use by qemu at that point -- not only did we report the (ACK|DRIVER|DRIVER_OK) status earlier, we even communicated over the ring. Of course SeaBIOS doesn't "kick" the HBA ever again, hence qemu has no reason to look at the ring. However, when qemu uses KVM acceleration, and ioeventfd is enabled for the HBA, then a vmstate change to "running" (including stop->cont monitor commands and incoming migration) "forces" a kick (see qemu commit 25db9ebe). Qemu then tries to interpret whatever unrelated guest data is in the HBA's original ring area, as virtio protocol. Qemu exits upon seeing the garbage. init_virtio_scsi() should reset the HBA before allowing the virtio ring memory to be reused. Device reset causes the hypervisor to drop its references. This change is justified / underpinned by pure virtio-spec compliance as well. Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1013418 Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions