memory: use find_next_bit() to find dirty bits

This operation is way faster than doing it bit by bit.

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:15:06 +02:00
parent ace694cccc
commit 1bafff0c7c
1 changed files with 6 additions and 10 deletions

View File

@ -44,19 +44,15 @@ static inline bool cpu_physical_memory_get_dirty(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, next;
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) { next = find_next_bit(ram_list.dirty_memory[client], end, page);
if (test_bit(addr >> TARGET_PAGE_BITS,
ram_list.dirty_memory[client])) { return next < end;
return true;
}
}
return false;
} }
static inline bool cpu_physical_memory_get_dirty_flag(ram_addr_t addr, static inline bool cpu_physical_memory_get_dirty_flag(ram_addr_t addr,