From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56735) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yg9wW-0008P2-NZ for qemu-devel@nongnu.org; Thu, 09 Apr 2015 06:44:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yg9wU-00070c-27 for qemu-devel@nongnu.org; Thu, 09 Apr 2015 06:44:16 -0400 Received: from mail-ig0-f182.google.com ([209.85.213.182]:37705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yg9wT-0006zY-U7 for qemu-devel@nongnu.org; Thu, 09 Apr 2015 06:44:13 -0400 Received: by igblo3 with SMTP id lo3so61120572igb.0 for ; Thu, 09 Apr 2015 03:44:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <552652AA.5070701@redhat.com> References: <1428437400-8474-1-git-send-email-peter.maydell@linaro.org> <1428437400-8474-7-git-send-email-peter.maydell@linaro.org> <20150409095904.GH30629@toto> <552652AA.5070701@redhat.com> From: Peter Maydell Date: Thu, 9 Apr 2015 11:43:53 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 06/14] exec.c: Make address_space_rw take transaction attributes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Peter Crosthwaite , Patch Tracking , QEMU Developers , Greg Bellows , "Edgar E. Iglesias" , =?UTF-8?B?QWxleCBCZW5uw6ll?= , Richard Henderson On 9 April 2015 at 11:21, Paolo Bonzini wrote: > > > On 09/04/2015 12:14, Peter Maydell wrote: >> On 9 April 2015 at 10:59, Edgar E. Iglesias wrote: >>> > On Tue, Apr 07, 2015 at 09:09:52PM +0100, Peter Maydell wrote: >>>> >> Make address_space_rw take transaction attributes, rather >>>> >> than always using the 'unspecified' attributes. >>> > >>> > Reviewed-by: Edgar E. Iglesias >>> > >>> > I guess that we eventually will need to convert the dma_ >>> > functions? >> Probably, though I'm not clear what they bring to the party >> that the basic address_space_* functions don't (part of why >> I left them alone). > > At this point, some memory barriers, basically. So what distinguishes a device that needs the memory barriers and does its accesses via dma_* from a device that doesn't and uses address_space_* or ld/st*_phys ? (Or for that matter a non-device that does memory accesses...) thanks -- PMM