| commit | aa90fec7ad128039617d31a5fd5ced8b0488f71b | |
| author | Benjamin Herrenschmidt <benh@kernel.crashing.org> | |
| Wed, 11 Jan 2012 19:46:21 +0000 (11 19:46 +0000) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Sat, 21 Jan 2012 04:17:01 +0000 (21 05:17 +0100) | ||
| tree | 58aec06f2ac508e483bbb75e6b40fcca4ded3a53 | treesnapshot (tar.gz zip) |
| parent | 17df768c1e4580f03301d18ea938d3557d441911 | commitdiff |
Fix dirty logging with 32-bit qemu & 64-bit guests
The kvm_get_dirty_pages_log_range() function uses two address
variables to step through the monitored memory region to update the
dirty log. However, these variables have type unsigned long, which
can overflow if running a 64-bit guest with a 32-bit qemu binary.
This patch changes these to target_phys_addr_t which will have the
correct size.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
The kvm_get_dirty_pages_log_range() function uses two address
variables to step through the monitored memory region to update the
dirty log. However, these variables have type unsigned long, which
can overflow if running a 64-bit guest with a 32-bit qemu binary.
This patch changes these to target_phys_addr_t which will have the
correct size.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
| kvm-all.c | diffblobblamehistory |