memory: cpu_physical_memory_clear_dirty_range() now uses bitmap operations

We were clearing a range of bits, so use bitmap_clear().

Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Orit Wasserman <owasserm@redhat.com>
This commit is contained in:
Juan Quintela 2013-10-09 12:30:35 +02:00
parent 5b9a3a5f77
commit a461e389f4
1 changed files with 4 additions and 6 deletions

View File

@ -95,14 +95,12 @@ static inline void cpu_physical_memory_clear_dirty_range(ram_addr_t start,
ram_addr_t length, ram_addr_t length,
unsigned client) unsigned client)
{ {
ram_addr_t addr, end; unsigned long end, page;
assert(client < DIRTY_MEMORY_NUM); assert(client < DIRTY_MEMORY_NUM);
end = TARGET_PAGE_ALIGN(start + length); end = TARGET_PAGE_ALIGN(start + length) >> TARGET_PAGE_BITS;
start &= TARGET_PAGE_MASK; page = start >> TARGET_PAGE_BITS;
for (addr = start; addr < end; addr += TARGET_PAGE_SIZE) { bitmap_clear(ram_list.dirty_memory[client], page, end - page);
clear_bit(addr >> TARGET_PAGE_BITS, ram_list.dirty_memory[client]);
}
} }
void cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t end, void cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t end,