[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API
From: |
Avi Kivity |
Subject: |
Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API |
Date: |
Thu, 04 Oct 2012 12:18:12 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 |
On 10/03/2012 10:26 PM, Blue Swirl wrote:
> On Wed, Oct 3, 2012 at 4:03 PM, Avi Kivity <address@hidden> 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
- Re: [Qemu-devel] [RFC v1 19/22] memory: per-AddressSpace dispatch, (continued)
[Qemu-devel] [RFC v1 17/22] memory: use AddressSpace for MemoryListener filtering, Avi Kivity, 2012/10/03
Re: [Qemu-devel] [RFC v1 17/22] memory: use AddressSpace for MemoryListener filtering, Anthony Liguori, 2012/10/04
[Qemu-devel] [RFC v1 18/22] s390: avoid reaching into memory core internals, Avi Kivity, 2012/10/03
Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API, Blue Swirl, 2012/10/03
- Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API,
Avi Kivity <=
Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API, Avi Kivity, 2012/10/04
Re: [Qemu-devel] [RFC v1 00/22] Integrate DMA into the memory API, Paolo Bonzini, 2012/10/04