| commit | 42af3e3a02f6d0c38c46465b7f0311eabf532f77 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 22 Apr 2015 11:30:19 +0000 (22 13:30 +0200) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Fri, 5 Jun 2015 15:09:59 +0000 (5 17:09 +0200) | ||
| tree | 788b5eacd52d02511fa4ff5f52fa236d59975555 | treesnapshot (tar.gz zip) |
| parent | d55d42078bfb507743747b761673507b95a76620 | commitdiff |
ui/console: remove dpy_gfx_update_dirty
dpy_gfx_update_dirty expects DIRTY_MEMORY_VGA logging to be always on,
but that will not be the case soon. Because it computes the memory
region on the fly for every update (with memory_region_find), it cannot
enable/disable logging by itself.
We could always treat updates as invalidations if dirty logging is
not enabled, assuming that the board will enable logging on the
RAM region that includes the framebuffer.
However, the function is unused, so just drop it.
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
dpy_gfx_update_dirty expects DIRTY_MEMORY_VGA logging to be always on,
but that will not be the case soon. Because it computes the memory
region on the fly for every update (with memory_region_find), it cannot
enable/disable logging by itself.
We could always treat updates as invalidations if dirty logging is
not enabled, assuming that the board will enable logging on the
RAM region that includes the framebuffer.
However, the function is unused, so just drop it.
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| include/ui/console.h | diffblobblamehistory | |
| ui/console.c | diffblobblamehistory |