From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y70Un-0003Zp-5S for qemu-devel@nongnu.org; Fri, 02 Jan 2015 06:34:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y70Ui-00088E-GF for qemu-devel@nongnu.org; Fri, 02 Jan 2015 06:34:21 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:59314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y70Ui-00087u-6U for qemu-devel@nongnu.org; Fri, 02 Jan 2015 06:34:16 -0500 Message-ID: <54A681EC.9010903@Vivier.EU> Date: Fri, 02 Jan 2015 12:33:00 +0100 From: Laurent Vivier MIME-Version: 1.0 References: <1419813550-26182-1-git-send-email-laurent@vivier.eu> <54A5B5A0.7000600@reactos.org> <54A5F5C0.4030402@Vivier.EU> <54A66408.3040406@Vivier.EU> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gDAhcc2laGUh8fwbEnq1R00CvemtRwSvh" Subject: Re: [Qemu-devel] [PATCH 0/3] dp8393x update List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Peter Crosthwaite , QEMU Developers , =?UTF-8?B?SGVydsOpIFBvdXNzaW5lYXU=?= , "Edgar E. Iglesias" , Leon Alrae , Aurelien Jarno This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gDAhcc2laGUh8fwbEnq1R00CvemtRwSvh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Le 02/01/2015 11:19, Peter Maydell a =C3=A9crit : > On 2 January 2015 at 09:25, Laurent Vivier wrote: >> Using AddressSpace is really a very good idea, in fact, but I don't li= ke >> 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. >=20 > 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 --gDAhcc2laGUh8fwbEnq1R00CvemtRwSvh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlSmgewACgkQNKT2yavzbFND7ACfclclO5b+PS+3GJ1dVjs0anKY kCAAoIuE9I60bnsXud5DV/USAr7MvVkI =MUUk -----END PGP SIGNATURE----- --gDAhcc2laGUh8fwbEnq1R00CvemtRwSvh--