From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPirP-0001za-Kw for qemu-devel@nongnu.org; Wed, 21 Jan 2009 14:35:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPirO-0001xr-Kl for qemu-devel@nongnu.org; Wed, 21 Jan 2009 14:35:34 -0500 Received: from [199.232.76.173] (port=41910 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPirO-0001xZ-Cp for qemu-devel@nongnu.org; Wed, 21 Jan 2009 14:35:34 -0500 Received: from mx2.redhat.com ([66.187.237.31]:54823) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LPirN-0003tr-Te for qemu-devel@nongnu.org; Wed, 21 Jan 2009 14:35:34 -0500 Message-ID: <49777919.7050307@redhat.com> Date: Wed, 21 Jan 2009 21:35:53 +0200 From: Avi Kivity 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> <49761B6A.2020806@codemonkey.ws> <18807.22215.857033.533504@mariner.uk.xensource.com> <20090121185629.GA326@silverwood.ncultra.org> In-Reply-To: <20090121185629.GA326@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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ncmike@ncultra.org, qemu-devel@nongnu.org Mike Day wrote: > cpu_physical_memory_rw will still be available and used by most > devices even with this proposed API, right? Certain devices will be > able to now use the new API. > Yes. When I converted IDE, for example, access to the scatter/gather list remains using cpu_p_m_rw(), while accessing the buffers pointed to by the lists uses the new API. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.