From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 4/7] memory: optimize empty transactions due to mutators
Date: Thu, 15 Dec 2011 17:18:36 +0200 [thread overview]
Message-ID: <1323962319-13762-5-git-send-email-avi@redhat.com> (raw)
In-Reply-To: <1323962319-13762-1-git-send-email-avi@redhat.com>
The mutating memory APIs can easily cause empty transactions,
where the mutators don't actually change anything, or perhaps
only modify disabled regions. Detect these conditions and
avoid regenerating the memory topology.
Signed-off-by: Avi Kivity <avi@redhat.com>
---
memory.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/memory.c b/memory.c
index 7e842b3..87639ab 100644
--- a/memory.c
+++ b/memory.c
@@ -19,6 +19,7 @@
#include <assert.h>
unsigned memory_region_transaction_depth = 0;
+static bool memory_region_update_pending = false;
typedef struct AddrRange AddrRange;
@@ -757,6 +758,7 @@ static void address_space_update_topology(AddressSpace *as)
static void memory_region_update_topology(MemoryRegion *mr)
{
if (memory_region_transaction_depth) {
+ memory_region_update_pending |= !mr || mr->enabled;
return;
}
@@ -770,6 +772,8 @@ static void memory_region_update_topology(MemoryRegion *mr)
if (address_space_io.root) {
address_space_update_topology(&address_space_io);
}
+
+ memory_region_update_pending = false;
}
void memory_region_transaction_begin(void)
@@ -781,7 +785,9 @@ void memory_region_transaction_commit(void)
{
assert(memory_region_transaction_depth);
--memory_region_transaction_depth;
- memory_region_update_topology(NULL);
+ if (!memory_region_transaction_depth && memory_region_update_pending) {
+ memory_region_update_topology(NULL);
+ }
}
static void memory_region_destructor_none(MemoryRegion *mr)
--
1.7.7.1
next prev parent reply other threads:[~2011-12-15 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 15:18 [Qemu-devel] [PULL v3 0/7] Memory API mutators Avi Kivity
2011-12-15 15:18 ` [Qemu-devel] [PATCH 1/7] memory: introduce memory_region_set_enabled() Avi Kivity
2011-12-15 15:18 ` [Qemu-devel] [PATCH 2/7] memory: introduce memory_region_set_address() Avi Kivity
2011-12-15 15:18 ` [Qemu-devel] [PATCH 3/7] memory: introduce memory_region_set_alias_offset() Avi Kivity
2011-12-15 15:18 ` Avi Kivity [this message]
2011-12-15 15:18 ` [Qemu-devel] [PATCH 5/7] cirrus_vga: adapt to memory mutators API Avi Kivity
2011-12-15 15:18 ` [Qemu-devel] [PATCH 6/7] piix_pci: adapt smram mapping to use memory mutators Avi Kivity
2011-12-15 15:18 ` [Qemu-devel] [PATCH 7/7] docs: document memory API interaction with migration Avi Kivity
2011-12-19 15:44 ` [Qemu-devel] [PULL v3 0/7] Memory API mutators Anthony Liguori
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=1323962319-13762-5-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).