From: Keqian Zhu <zhukeqian1@huawei.com>
To: Peter Xu <peterx@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
jiangkunkun@huawei.com, qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
qemu-arm@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Zenghui Yu <yuzenghui@huawei.com>,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH 1/2] accel: kvm: Fix memory waste under mismatch page size
Date: Wed, 16 Dec 2020 16:21:17 +0800 [thread overview]
Message-ID: <8a23c62d-1167-d005-e98b-14507e15fbf2@huawei.com> (raw)
In-Reply-To: <20201215175719.GA112585@xz-x1>
Hi Peter,
On 2020/12/16 1:57, Peter Xu wrote:
> On Tue, Dec 15, 2020 at 03:19:47PM +0800, Keqian Zhu wrote:
>> When handle dirty log, we face qemu_real_host_page_size and
>> TARGET_PAGE_SIZE. The first one is the granule of KVM dirty
>> bitmap, and the second one is the granule of QEMU dirty bitmap.
>>
>> Generally speaking, qemu_real_host_page_size >= TARGET_PAGE_SIZE,
>> so misuse TARGET_PAGE_SIZE to init kvmslot dirty_bmap may waste
>> memory. For example, when qemu_real_host_page_size is 64K and
>> TARGET_PAGE_SIZE is 4K, this bugfix can save 93.75% memory.
>>
>> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
>> ---
>> accel/kvm/kvm-all.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
>> index baaa54249d..c5e06288eb 100644
>> --- a/accel/kvm/kvm-all.c
>> +++ b/accel/kvm/kvm-all.c
>> @@ -620,8 +620,12 @@ static void kvm_memslot_init_dirty_bitmap(KVMSlot *mem)
>> * too, in most cases).
>> * So for now, let's align to 64 instead of HOST_LONG_BITS here, in
>> * a hope that sizeof(long) won't become >8 any time soon.
>> + *
>> + * Note: the granule of kvm dirty log is qemu_real_host_page_size.
>> + * And mem->memory_size is aligned to it (otherwise this mem can't
>> + * be registered to KVM).
>> */
>> - hwaddr bitmap_size = ALIGN(((mem->memory_size) >> TARGET_PAGE_BITS),
>> + hwaddr bitmap_size = ALIGN(mem->memory_size / qemu_real_host_page_size,
>> /*HOST_LONG_BITS*/ 64) / 8;
>
> Yes I think this is correct. Thanks.
>
> So one thing I failed to notice is cpu_physical_memory_set_dirty_lebitmap()
> will "amplify" the host dirty pages into guest ones; seems we're all good then.
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
OK Thanks :-)
One more thing, we should consider whether @start and @size is psize aligned (my second
patch). Do you agree to add assert on them directly?
Thanks,
Keqian
next prev parent reply other threads:[~2020-12-16 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 7:19 [PATCH 0/2] accel: kvm: Some bugfixes for kvm dirty log Keqian Zhu
2020-12-15 7:19 ` [PATCH 1/2] accel: kvm: Fix memory waste under mismatch page size Keqian Zhu
2020-12-15 11:20 ` Andrew Jones
2020-12-16 8:08 ` Keqian Zhu
2020-12-15 17:57 ` Peter Xu
2020-12-16 8:21 ` Keqian Zhu [this message]
2020-12-16 20:48 ` Peter Xu
2020-12-17 1:03 ` Keqian Zhu
2020-12-15 7:19 ` [PATCH 2/2] accel: kvm: Add aligment check for kvm_log_clear_one_slot Keqian Zhu
2020-12-15 11:55 ` Andrew Jones
2020-12-16 7:23 ` Andrew Jones
2020-12-16 8:17 ` Keqian Zhu
2020-12-16 8:11 ` Keqian Zhu
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=8a23c62d-1167-d005-e98b-14507e15fbf2@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=dgilbert@redhat.com \
--cc=jiangkunkun@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@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).