From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgAsd-0004P4-8c for qemu-devel@nongnu.org; Thu, 09 Apr 2015 07:44:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YgAsZ-0005D8-1C for qemu-devel@nongnu.org; Thu, 09 Apr 2015 07:44:19 -0400 Received: from mail-ig0-f172.google.com ([209.85.213.172]:37678) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgAsY-0005Ck-Sc for qemu-devel@nongnu.org; Thu, 09 Apr 2015 07:44:14 -0400 Received: by igblo3 with SMTP id lo3so62128115igb.0 for ; Thu, 09 Apr 2015 04:44:14 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <5526651F.7080908@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> <5526651F.7080908@redhat.com> From: Peter Maydell Date: Thu, 9 Apr 2015 12:43:54 +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 12:40, Paolo Bonzini wrote: > > > On 09/04/2015 12:43, Peter Maydell wrote: >> > 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...) > > I don't know exactly, I didn't follow the discussion very much back > then. The memory barriers were fixing PPC bugs; PCI devices definitely > need them. I suspect that actually we need barriers in a lot more places and there shouldn't really be a separate set of APIs here; it's just that nobody's tried using the wider set of devices in PPC KVM systems. -- PMM