From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LPc2Y-0003D4-81
	for qemu-devel@nongnu.org; Wed, 21 Jan 2009 07:18:39 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LPc2X-0003Cb-2Q
	for qemu-devel@nongnu.org; Wed, 21 Jan 2009 07:18:37 -0500
Received: from [199.232.76.173] (port=58425 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LPc2V-0003CS-4U
	for qemu-devel@nongnu.org; Wed, 21 Jan 2009 07:18:35 -0500
Received: from mx2.redhat.com ([66.187.237.31]:53594)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1LPc2U-0002Wd-Px
	for qemu-devel@nongnu.org; Wed, 21 Jan 2009 07:18:35 -0500
Message-ID: <49771295.2000203@redhat.com>
Date: Wed, 21 Jan 2009 14:18:29 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Add target memory mapping API
References: <1232308399-21679-1-git-send-email-avi@redhat.com>	<1232308399-21679-2-git-send-email-avi@redhat.com>	<18804.34053.211615.181730@mariner.uk.xensource.com>	<4974943B.4020507@redhat.com>	<18804.44271.868488.32192@mariner.uk.xensource.com>	<4974B82F.9020805@redhat.com>
	<20090121120630.GB12504@silverwood.ncultra.org>
In-Reply-To: <20090121120630.GB12504@silverwood.ncultra.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: ncmike@ncultra.org, qemu-devel@nongnu.org

Mike Day wrote:
>> What is the motivation for efficient rmw?
>>     
>
> rmw would be good for changing bytes in a device config space, or
> programming an IOMMU. Right now these are not on the critical path but
> they may be soon in some cases. For example imagine an assigned I/O
> device that wants to dynamically map io translations for each DMA.
>   

You don't do these with dma, instead you use cpu instructions which go 
through cpu_physical_memory_rw().

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