[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 02/16] migration: Correct transferred bytes value
From: |
Juan Quintela |
Subject: |
Re: [PATCH v2 02/16] migration: Correct transferred bytes value |
Date: |
Tue, 30 May 2023 12:30:41 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Leonardo Bras Soares Passos <leobras@redhat.com> wrote:
> On Fri, May 26, 2023 at 5:04 AM Juan Quintela <quintela@redhat.com> wrote:
>> > Maybe too much?
>>
>> I dropped this patch for two reasons:
>>
>> - reviewers gave me a bad time with it O:-)
>> - it was there only so if anyone was meassuring that new counters are
>> the same that old counters.
>>
>> But as I have already checked that, we don't need it.
>>
>> I drop it on the next round that I send.
>> > Maybe, it would be nice to have qemu_put_* to return the value, and in this
>> > case:
>> >
>> > size += qemu_put_be64(...)
>> >
>> > What do you think?
>>
>> Even more important than that is to return an error value, but that
>> is a very long project.
>>
>> See on my next series that qemu_fflush() return errors, so code gets
>> simplifed:
>>
>> qemu_fflush(file);
>> if (qemu_file_get_error(file)) {
>> handle error;
>> }
>>
>> to:
>>
>> qemu_fflush(file);
>> if (qemu_file_get_error(file)) {
>> handle error;
>> }
>>
>
> They look the same to me, what changed?
I did copy paste without changing:
if (qemu_fflush(file)) {
handle error;
}
>> We need to do basically all qemu_put_*() and qemu_get_*() functions, but
>> it is a step on the right direction.
>>
>> Later, Juan.
>>
- Re: [PATCH v2 01/16] migration: Don't use INT64_MAX for unlimited rate, (continued)
[PATCH v2 02/16] migration: Correct transferred bytes value, Juan Quintela, 2023/05/15
[PATCH v2 03/16] migration: Move setup_time to mig_stats, Juan Quintela, 2023/05/15
Re: [PATCH v2 03/16] migration: Move setup_time to mig_stats, Leonardo Brás, 2023/05/24
[PATCH v2 05/16] migration: Move rate_limit_max and rate_limit_used to migration_stats, Juan Quintela, 2023/05/15