Re: [PATCH 2/2] virDomainGetBlockJobInfo: Fix corner case when qemu reports no info

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13.09.2016 19:03, Eric Blake wrote:
> On 09/13/2016 06:02 AM, Michal Privoznik wrote:
> 
>>> So, just to make it crystal clear, is this what you're saying?
>>>
>>> ready | initial C/R |fudged C/R
>>
>> Oh, This should have been C/E instead of C/R. Current/End. 'e' and 'r'
>> keys are just too close to each other :-)
>>
>>> ------+-------------+----------
>>>  < 0  |     0/0     |   0/0
>>>  = 0  |	    0/0     |   0/1
>>>  > 0  |	    0/0     |   1/1
> 
> Yes, I think that's the best. Then we have documented to apps higher in
> the stack that if they see 0/0, it is because qemu is too old to give us
> a definitive answer; in all other cases, we have fudged data so that
> higher layers don't have to worry about 0/0.
> 

Thank you guys, I've pushed the patch then (with the behaviour as
described in the table).

Michal

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]