Am 15.08.2018 um 16:44 hat Peter Krempa geschrieben: > On Tue, Aug 07, 2018 at 00:33:28 -0400, John Snow wrote: > > This series forces all jobs to use the "finalize" semantics that were > > introduced previously, but only exposed via the backup jobs. > > This series looks huge, but it's mostly mechanical changes broken out > > into a series of much smaller commits so that the changes are easier > > to follow at each step. > > Please note that due to the semantics of the commands 'block-job-cancel' > and 'block-job-complete' at least in case of the drive/blockdev-mirror > job are technically blockjobs of it's own since they may fail or finish > in an unbounded amount of time and the actual return value on the > monitor does not reflect the result of the operation itself. > > It would be very helpful if qemu treas them as such.
'block-job-cancel' and 'block-job-complete' return immediately. They just move the given job into the next phase and return. That job may then still take some time until it finally completes (successfully or with an error), but that's not part of 'block-job-cancel/complete' any more. Kevin
signature.asc
Description: PGP signature
