From: Peter Xu <peterx@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
qemu-stable@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v1] softmmu/physmem: fix memory leak in dirty_memory_extend()
Date: Tue, 27 Aug 2024 13:57:04 -0400 [thread overview]
Message-ID: <Zs4TcHvfwhBFSWvQ@x1n> (raw)
In-Reply-To: <20240827083715.257768-1-david@redhat.com>
On Tue, Aug 27, 2024 at 10:37:15AM +0200, David Hildenbrand wrote:
> /* Called with ram_list.mutex held */
> -static void dirty_memory_extend(ram_addr_t old_ram_size,
> - ram_addr_t new_ram_size)
> +static void dirty_memory_extend(ram_addr_t new_ram_size)
> {
> - ram_addr_t old_num_blocks = DIV_ROUND_UP(old_ram_size,
> - DIRTY_MEMORY_BLOCK_SIZE);
> ram_addr_t new_num_blocks = DIV_ROUND_UP(new_ram_size,
> DIRTY_MEMORY_BLOCK_SIZE);
> int i;
>
> - /* Only need to extend if block count increased */
> - if (new_num_blocks <= old_num_blocks) {
> - return;
> - }
One nitpick here: IMHO we could move the n_blocks cache in ram_list
instead, then we keep the check here and avoid caching it three times with
the same value.
> -
> for (i = 0; i < DIRTY_MEMORY_NUM; i++) {
> DirtyMemoryBlocks *old_blocks;
> DirtyMemoryBlocks *new_blocks;
> + ram_addr_t old_num_blocks = 0;
> int j;
>
> old_blocks = qatomic_rcu_read(&ram_list.dirty_memory[i]);
> + if (old_blocks) {
> + old_num_blocks = old_blocks->num_blocks;
> +
> + /* Only need to extend if block count increased */
> + if (new_num_blocks <= old_num_blocks) {
> + return;
> + }
> + }
--
Peter Xu
next prev parent reply other threads:[~2024-08-27 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 8:37 [PATCH v1] softmmu/physmem: fix memory leak in dirty_memory_extend() David Hildenbrand
2024-08-27 16:16 ` Peter Maydell
2024-08-27 16:52 ` Stefan Hajnoczi
2024-08-27 17:23 ` David Hildenbrand
2024-08-27 17:28 ` Stefan Hajnoczi
2024-08-27 17:50 ` Peter Xu
2024-08-27 17:55 ` David Hildenbrand
2024-08-27 17:57 ` Peter Xu [this message]
2024-08-27 18:00 ` David Hildenbrand
2024-08-27 18:41 ` Peter Xu
2024-08-28 7:20 ` David Hildenbrand
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=Zs4TcHvfwhBFSWvQ@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.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).