提交 93102fd6 编写于 作者: J Jan Kiszka 提交者: Anthony Liguori

kvm: Fix framebuffer dirty log sync

kvm_physical_sync_dirty_bitmap() takes the end address as second
argument, not the region size. Moverover, the kvm API should not be used
directly here, but cpu_physical_sync_dirty_bitmap().
Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
上级 b0a46a33
......@@ -17,7 +17,6 @@
#include "hw.h"
#include "console.h"
#include "framebuffer.h"
#include "kvm.h"
/* Render an image from a shared memory framebuffer. */
......@@ -50,9 +49,7 @@ void framebuffer_update_display(
*first_row = -1;
src_len = src_width * rows;
if (kvm_enabled()) {
kvm_physical_sync_dirty_bitmap(base, src_len);
}
cpu_physical_sync_dirty_bitmap(base, base + src_len);
pd = cpu_get_physical_page_desc(base);
pd2 = cpu_get_physical_page_desc(base + src_len - 1);
/* We should reall check that this is a continuous ram region.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册