qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>,
	pbonzini@redhat.com, imammedo@redhat.com, dgilbert@redhat.com,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v3 2/8] exec: cpu_physical_memory_set/clear_dirty_range
Date: Wed, 7 Jan 2015 21:48:53 +0200	[thread overview]
Message-ID: <1420660083-9961-3-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1420660083-9961-1-git-send-email-mst@redhat.com>

Make cpu_physical_memory_set/clear_dirty_range
behave symmetrically.

To clear range for a given client type only, add
cpu_physical_memory_clear_dirty_range_type.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 include/exec/ram_addr.h | 15 ++++++++++++---
 exec.c                  |  2 +-
 2 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/include/exec/ram_addr.h b/include/exec/ram_addr.h
index 8fc75cd..254931c 100644
--- a/include/exec/ram_addr.h
+++ b/include/exec/ram_addr.h
@@ -172,9 +172,9 @@ static inline void cpu_physical_memory_set_dirty_lebitmap(unsigned long *bitmap,
 }
 #endif /* not _WIN32 */
 
-static inline void cpu_physical_memory_clear_dirty_range(ram_addr_t start,
-                                                         ram_addr_t length,
-                                                         unsigned client)
+static inline void cpu_physical_memory_clear_dirty_range_type(ram_addr_t start,
+                                                              ram_addr_t length,
+                                                              unsigned client)
 {
     unsigned long end, page;
 
@@ -184,6 +184,15 @@ static inline void cpu_physical_memory_clear_dirty_range(ram_addr_t start,
     bitmap_clear(ram_list.dirty_memory[client], page, end - page);
 }
 
+static inline void cpu_physical_memory_clear_dirty_range(ram_addr_t start,
+                                                         ram_addr_t length)
+{
+    cpu_physical_memory_clear_dirty_range_type(start, length, DIRTY_MEMORY_MIGRATION);
+    cpu_physical_memory_clear_dirty_range_type(start, length, DIRTY_MEMORY_VGA);
+    cpu_physical_memory_clear_dirty_range_type(start, length, DIRTY_MEMORY_CODE);
+}
+
+
 void cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t length,
                                      unsigned client);
 
diff --git a/exec.c b/exec.c
index 963481a..a89aa6c 100644
--- a/exec.c
+++ b/exec.c
@@ -850,7 +850,7 @@ void cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t length,
 {
     if (length == 0)
         return;
-    cpu_physical_memory_clear_dirty_range(start, length, client);
+    cpu_physical_memory_clear_dirty_range_type(start, length, client);
 
     if (tcg_enabled()) {
         tlb_reset_dirty_range_all(start, length);
-- 
MST

  parent reply	other threads:[~2015-01-07 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 19:48 [Qemu-devel] [PATCH v3 0/8] acpi: make ROMs resizeable Michael S. Tsirkin
2015-01-07 19:48 ` [Qemu-devel] [PATCH v3 1/8] memory: add memory_region_set_size Michael S. Tsirkin
2015-01-07 19:48 ` Michael S. Tsirkin [this message]
2015-01-07 19:48 ` [Qemu-devel] [PATCH v3 3/8] exec: split length -> used_length/max_length Michael S. Tsirkin
2015-01-07 19:49 ` [Qemu-devel] [PATCH v3 4/8] exec: qemu_ram_alloc_resizeable, qemu_ram_resize Michael S. Tsirkin
2015-01-07 19:49 ` [Qemu-devel] [PATCH v3 5/8] arch_init: support resizing on incoming migration Michael S. Tsirkin
2015-01-07 19:49 ` [Qemu-devel] [PATCH v3 6/8] memory: API to allocate resizeable RAM MR Michael S. Tsirkin
2015-01-07 19:49 ` [Qemu-devel] [PATCH v3 7/8] acpi-build: make ROMs RAM blocks resizeable Michael S. Tsirkin
2015-01-07 19:49 ` [Qemu-devel] [PATCH v3 8/8] qemu_ram_resize: document assumptions Michael S. Tsirkin
2015-01-07 20:48 ` [Qemu-devel] [PATCH v3 0/8] acpi: make ROMs resizeable Paolo Bonzini

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=1420660083-9961-3-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).