From: Juan Quintela <quintela@redhat.com>
To: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
Cc: qemu-devel@nongnu.org, xuquan8@huawei.com, lvivier@redhat.com,
dgilbert@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock
Date: Wed, 26 Apr 2017 12:53:23 +0200 [thread overview]
Message-ID: <87shkvjv8c.fsf@secure.mitica> (raw)
In-Reply-To: <5900603E.4040606@huawei.com> (Hailiang Zhang's message of "Wed, 26 Apr 2017 16:54:22 +0800")
Hailiang Zhang <zhang.zhanghailiang@huawei.com> wrote:
> On 2017/4/26 15:32, Juan Quintela wrote:
>> Both the ram bitmap and the unsent bitmap are split by RAMBlock.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>>
>> --
>>
>> Fix compilation when DEBUG_POSTCOPY is enabled (thanks Hailiang)
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> + postcopy_chunk_hostpages_pass(ms, false, block, pds);
>> +
>> + postcopy_discard_send_finish(ms, pds);
>> return 0;
>
> It always return 0 here for postcopy_chunk_hostpages(), so change it to void ?
This was dave code. I assume that he has in mind something where it can
fail?
>> + /* Deal with TPS != HPS and huge pages */
>> + ret = postcopy_chunk_hostpages(ms, block);
>> + if (ret) {
>
> It will never go here, see above.
Yeap, I also noticed.
>> + bitmap_or(unsentmap, unsentmap, bitmap, pages);
>> #ifdef DEBUG_POSTCOPY
>> - ram_debug_dump_bitmap(unsentmap, true);
>> + ram_debug_dump_bitmap(unsentmap, true, pages);
> Indent, you use tab here.
Fixed.
> Others look good to me.
>
> Reviewed-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Thanks.
next prev parent reply other threads:[~2017-04-26 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 7:32 [Qemu-devel] [PATCH v5] Split migration bitmaps by ramblock Juan Quintela
2017-04-26 7:32 ` [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock Juan Quintela
2017-04-26 8:54 ` Hailiang Zhang
2017-04-26 10:53 ` Juan Quintela [this message]
2017-04-26 9:16 ` Peter Xu
2017-04-26 10:57 ` no-reply
-- strict thread matches above, loose matches on Subject: below --
2017-04-25 10:11 [Qemu-devel] [PATCH v4] Split migration bitmaps by ramblock Juan Quintela
2017-04-25 10:11 ` [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock Juan Quintela
2017-04-25 11:54 ` Hailiang Zhang
2017-04-25 13:00 ` Juan Quintela
2017-04-19 21:06 [Qemu-devel] [PATCH v3] Split migration bitmaps by ramblock Juan Quintela
2017-04-19 21:06 ` [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock Juan Quintela
2017-04-20 12:36 ` Dr. David Alan Gilbert
2017-03-23 21:01 [Qemu-devel] [RFC] Split migration bitmaps by ramblock Juan Quintela
2017-03-23 21:01 ` [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shkvjv8c.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xuquan8@huawei.com \
--cc=zhang.zhanghailiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).