On 07/02/2014 09:03 AM, Paolo Bonzini wrote: >>>> What if an underlying device doesn't support [rw]error=stop? Not all >>>> do... >>> >>> Then the "fix" is to add support to the underlying device. IDE, SCSI >>> and virtio-blk (plus virtio-scsi via SCSI of course) are covered; >> >> Where "covered" means "device model calls bdrv_error_action() somewhere" >> rather than "device model calls bdrv_error_action() exactly when it >> should". >> >> Case in point: SCSI calls it when UNMAP fails, but IDE doesn't call it >> when TRIM fails. IDE and virtio-blk call it for I/O beyond the end of >> the medium, but SCSI doesn't. >> >> This is of course fixable. I'm working on it. >> >>> the >>> main one that's left out is SD. >> >> Qdevified devices with a qdev_prop_drive: isa-fdc, sysbus-fdc, >> SUNW,fdtwo, nand, onenand, cfi.pflash01, cfi.pflash02, spapr-nvram, >> scsi-generic, nvme. SD isn't in this list, because it still hasn't been >> qdevified. There may be more. > > I think there is a page with unfinished transition. Can you add this one?
Listed: http://wiki.qemu.org/CodeTransitions#Reliable_block_job_polling -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
