qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v5 1/2] pl330: Initial version


From: Avi Kivity
Subject: Re: [Qemu-devel] [PATCH v5 1/2] pl330: Initial version
Date: Tue, 30 Oct 2012 15:57:00 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1

On 10/30/2012 03:42 PM, Peter Crosthwaite wrote:
> On Tue, Oct 30, 2012 at 7:51 PM, Avi Kivity <address@hidden> wrote:
>> On 10/29/2012 10:32 AM, Peter Maydell wrote:
>>> On 29 October 2012 06:35, Peter Crosthwaite
>>> <address@hidden> wrote:
>>>> Device model for Primecell PL330 dma controller.
>>>
>>> A general question -- this is a DMA controller so should it be using
>>> the DMAContext APIs now? Avi?
>>
>> IOMMU functionality will be folded into the memory core, so
>> address_space_rw() and family.
>>
>>
> 
> Hi Avi,
> 
> So does this mean no more dma_contexts and dma_memory_foo? 

Correct.

> I have
> remade the series (and others) using dma_memory_*. Can you point to a
> sysbus attached DMA controller currently in tree that does it properly
> so we can use it for a basis as there are several (four in total
> think) series I have pending all containing DMA which will be effected
> by this.

I don't think there are any.

If your dma controller does not have an IOMMU, all you need to do is
replace cpu_physical_memory_*(...) with
address_space_*(&address_space_memory, ...).  If it does have an IOMMU,
then you need to wait until my IOMMU patchset hits mainline (or use
DMAContext).



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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]