From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59421) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJiVX-0008Qk-FU for qemu-devel@nongnu.org; Thu, 04 Oct 2012 06:18:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TJiVW-0000qJ-GZ for qemu-devel@nongnu.org; Thu, 04 Oct 2012 06:18:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47325) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJiVW-0000qA-8c for qemu-devel@nongnu.org; Thu, 04 Oct 2012 06:18:18 -0400 Message-ID: <506D6264.2090206@redhat.com> Date: Thu, 04 Oct 2012 12:18:12 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1349280245-16341-1-git-send-email-avi@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: Paolo Bonzini , "Michael S. Tsirkin" , qemu-devel@nongnu.org, Anthony Liguori , liu ping fan On 10/03/2012 10:26 PM, Blue Swirl wrote: > On Wed, Oct 3, 2012 at 4:03 PM, Avi Kivity wrote: >> Most of the work on the memory API focused on memory access targets - the memory regions >> and how they are composed into an address space. This patchset tackles the initator >> side of the question - how to originate accesses. >> >> The AddressSpace object, is exported to users and becomes the representation of an >> initiator. Each address space describes the paths from some point in the system >> (a device or cpu) to the devices reachable from that initiator. >> >> As an example, the API is used to support PCI_COMMAND_MASTER bit. > > Excellent patches with high cleanup potential. Thanks. The next steps are memory_region_init_iommu() and the replacement of DMAContext with AddressSpace. -- error compiling committee.c: too many arguments to function