From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51878) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TYZZr-0002Qg-VI for qemu-devel@nongnu.org; Wed, 14 Nov 2012 04:48:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TYZZo-0007Wt-Qa for qemu-devel@nongnu.org; Wed, 14 Nov 2012 04:48:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47906) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TYZZo-0007Wn-Id for qemu-devel@nongnu.org; Wed, 14 Nov 2012 04:48:08 -0500 Message-ID: <50A368CD.1080002@redhat.com> Date: Wed, 14 Nov 2012 10:47:57 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1914486608.9887816.1352801368641.JavaMail.root@redhat.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v6 1/8] atomic: introduce atomic operations List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: liu ping fan Cc: Peter Maydell , Stefan Hajnoczi , Marcelo Tosatti , qemu-devel@nongnu.org, Avi Kivity , Anthony Liguori , Jan Kiszka Il 14/11/2012 10:38, liu ping fan ha scritto: > On Tue, Nov 13, 2012 at 6:11 PM, Paolo Bonzini wr= ote: >>>> Il 05/11/2012 06:38, Liu Ping Fan ha scritto: >>>>> From: Liu Ping Fan >>>>> >>>>> If out of global lock, we will be challenged by SMP in low level, >>>>> so need atomic ops. >>>>> >>>>> This file is a wrapper of GCC atomic builtin. >>>> >>>> I still object to this. >>>> >>>> I know it enforces type-safety, but it is incomplete. It doesn't >>> >>> Although it is incomplete, but the rest cases are rarely used. Linux >>> faces such issue, and the "int" version is enough, so I think we can >>> borrow experience from there. >> >> One of the two places that use __sync_* require 64-bit accesses. My > Yes, these two places are not easy to fix. Which shows that Linux's atomic_t is not suited for QEMU, in my opinion. >> RCU prototype required pointer-sized access, which you cannot make typ= e- > But I think that your RCU prototype should rely on atomic of CPU, not > gcc=91s atomic. What's the difference? gcc's atomic produces the same instructions as hand-written assembly (or should). > Otherwise, it could be slow (I guess something like spinlock there). Not sure what you mean. I'm using two things: 1) write barriers; 2) atomic_xchg of a pointer for fast, wait-free enqueuing of call_rcu callbacks. Paolo