From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 1/2] memory: Inherit has_coalesced_range from the same old FlatRange
Date: Tue, 20 Aug 2019 13:16:14 +0800 [thread overview]
Message-ID: <20190820051615.1210-2-peterx@redhat.com> (raw)
In-Reply-To: <20190820051615.1210-1-peterx@redhat.com>
The previous has_coalesced_range counter has a problem in that it only
works for additions of coalesced mmio ranges but not deletions. The
reason is that has_coalesced_range information can be lost when the
FlatView updates the topology again when the updated region is not
covering the coalesced regions. When that happens, due to
flatrange_equal() is not checking against has_coalesced_range, the new
FlatRange will be seen as the same one as the old and the new
instance (whose has_coalesced_range will be zero) will replace the old
instance (whose has_coalesced_range _could_ be non-zero).
To fix it, we inherit the has_coalesced_range value from the old
FlatRange to the new one if it's describing the identical range when
updating the topology.
Without this patch, MemoryListener.coalesced_io_del is hardly being
called due to has_coalesced_range will be mostly zero in
flat_range_coalesced_io_del() when topologies frequently change for
the "memory" address space.
Fixes: 3ac7d43a6fbb5d4a3
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
---
memory.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/memory.c b/memory.c
index 8141486832..c53dcfc092 100644
--- a/memory.c
+++ b/memory.c
@@ -939,6 +939,15 @@ static void address_space_update_topology_pass(AddressSpace *as,
/* In both and unchanged (except logging may have changed) */
if (adding) {
+ /*
+ * We must inherit the has_coalesced_range information
+ * if the new FlatRange is exactly the same as the old
+ * one, because it'll be used to conditionally call
+ * the coalesced mmio deletion listeners correctly in
+ * flat_range_coalesced_io_del() when the FlatRange
+ * needs to really go away.
+ */
+ frnew->has_coalesced_range = frold->has_coalesced_range;
MEMORY_LISTENER_UPDATE_REGION(frnew, as, Forward, region_nop);
if (frnew->dirty_log_mask & ~frold->dirty_log_mask) {
MEMORY_LISTENER_UPDATE_REGION(frnew, as, Forward, log_start,
--
2.21.0
next prev parent reply other threads:[~2019-08-20 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 5:16 [Qemu-devel] [PATCH v2 0/2] memory: Fix up coalesced_io_del not working for KVM Peter Xu
2019-08-20 5:16 ` Peter Xu [this message]
2019-08-20 5:16 ` [Qemu-devel] [PATCH v2 2/2] memory: Split zones when do coalesced_io_del() Peter Xu
2019-08-20 6:24 ` Paolo Bonzini
2019-08-20 6:35 ` Peter Xu
2019-08-20 6:37 ` Peter Xu
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=20190820051615.1210-2-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).