On 06/24/2012 05:08 PM, Jan Kiszka wrote: > As a first step, I will post a series later that gets rid of > kvm_flush_coalesced_mmio_buffer in the common vmexit path.
If you defer this, I can think of two places that need to flush: - anything that accesses those memory areas (such as DMA to the framebuffer, or updating the display) - anything that modifies the memory map and possibly changes flushed addresses -- error compiling committee.c: too many arguments to function
