exec: Fix qemu_ram_block_from_host for Xen
Since f615f39
(exec: remove ram_addr argument from
qemu_ram_block_from_host), migration under Xen is likely to fail, with a
SEGV of QEMU. But the commit only reveal a bug with the calculation of
the offset value in qemu_ram_block_from_host().
This patch calculates the offset from the ram_addr as
qemu_ram_addr_from_host() will later calculate the ram_addr from the
offset.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
This commit is contained in:
parent
a93c1bdf0b
commit
d6b6aec409
2
exec.c
2
exec.c
@ -1935,7 +1935,7 @@ RAMBlock *qemu_ram_block_from_host(void *ptr, bool round_offset,
|
|||||||
ram_addr = xen_ram_addr_from_mapcache(ptr);
|
ram_addr = xen_ram_addr_from_mapcache(ptr);
|
||||||
block = qemu_get_ram_block(ram_addr);
|
block = qemu_get_ram_block(ram_addr);
|
||||||
if (block) {
|
if (block) {
|
||||||
*offset = (host - block->host);
|
*offset = ram_addr - block->offset;
|
||||||
}
|
}
|
||||||
rcu_read_unlock();
|
rcu_read_unlock();
|
||||||
return block;
|
return block;
|
||||||
|
Loading…
Reference in New Issue
Block a user