|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH] kvm: First step to push iothread lock out of inner run loop |
Date: | Sun, 24 Jun 2012 17:35:11 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |