[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 0/3] dp8393x update
|
From: |
Laurent Vivier |
|
Subject: |
Re: [Qemu-devel] [PATCH 0/3] dp8393x update |
|
Date: |
Fri, 02 Jan 2015 12:33:00 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
Le 02/01/2015 11:19, Peter Maydell a écrit :
> On 2 January 2015 at 09:25, Laurent Vivier <address@hidden> wrote:
>> Using AddressSpace is really a very good idea, in fact, but I don't like
>> the way you pass it to the device (a qdev_set_prop()).
>>
>> I think we should do as it is done in PCI. This must be managed at
>> sysbus level, not at the device level.
>
> Actually I think using properties is the direction we're
> headed for this currently. (Consider the case of a sysbus
> device which has two DMA master ports, like an ARM trustzone
Does it means that these two DMA master ports can access different
address spaces ?
> aware device.) However I have a feeling the plan was to use
> MemoryRegion properties rather than AddressSpaces.
Is it possible to use something like dma_memory_rw() with MemoryRegion ?
Regards,
Laurent
signature.asc
Description: OpenPGP digital signature