From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:56630)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SioIS-0001OX-C7
	for qemu-devel@nongnu.org; Sun, 24 Jun 2012 11:00:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SioIQ-0007sw-MW
	for qemu-devel@nongnu.org; Sun, 24 Jun 2012 11:00:15 -0400
Received: from mx1.redhat.com ([209.132.183.28]:53043)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SioIQ-0007sc-EF
	for qemu-devel@nongnu.org; Sun, 24 Jun 2012 11:00:14 -0400
Message-ID: <4FE72B6E.8040900@redhat.com>
Date: Sun, 24 Jun 2012 17:59:58 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4FE4F56D.1020201@web.de> <4FE4F7F5.7030400@web.de>
	<20120623002259.GA13440@amt.cnet>
	<20120623090646.GA21908@amt.cnet> <4FE5AC75.1020504@web.de>
	<CAJnKYQkcV+a568srM73n=LqtB5EAjtPiwazQKo-=LHF+SVocMw@mail.gmail.com>
	<4FE71F71.7030908@web.de> <4FE7259F.4030100@redhat.com>
	<4FE726CF.5090906@web.de> <4FE72838.9070301@redhat.com>
	<4FE72980.5030807@web.de> <4FE72AA5.5070203@redhat.com>
	<4FE72B0C.5060908@web.de>
In-Reply-To: <4FE72B0C.5060908@web.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] kvm: First step to push iothread lock out
 of inner run loop
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Liu Ping Fan <pingfank@linux.vnet.ibm.com>, kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>, Marcelo Tosatti <mtosatti@redhat.com>, Alexander Graf <agraf@suse.de>, liu ping fan <qemulist@gmail.com>, Anthony Liguori <anthony@codemonkey.ws>

On 06/24/2012 05:58 PM, Jan Kiszka wrote:

>>> Are there really cases where the framebuffer is accessible both via MMIO
>>> and RAM-like mappings at the same time? If so, the current flushing on
>>> vmexit would help either as the direct mappings would not trigger exits.
>>> Or what do you mean?
>> 
>> I meant accesses by the display code to put the framebuffer in front of
>> the user's eyes.  Those just access the memory directly.  We could wrap
>> them with memory_region_get/put_ram_ptr() (as Xen requires anyway) and
>> have those issue the flush.
> 
> That's a non issue, we already have to flush on display updates. See
> e.g. vga_update_display.
> 

Ah, of course.


-- 
error compiling committee.c: too many arguments to function