From: Andi Kleen Subject: Re: [RFC PATCH 02/33] Add sync bitops Date: Wed, 19 Jul 2006 14:54:40 +0200 Message-ID: <200607191454.41019.ak@suse.de> References: <20060718091807.467468000@sous-sol.org> <20060718091948.747619000@sous-sol.org> <1153216601.3038.16.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1153216601.3038.16.camel@laptopd505.fenrus.org> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: Arjan van de Ven Cc: Chris Wright , linux-kernel@vger.kernel.org, virtualization@lists.osdl.org, xen-devel@lists.xensource.com, Jeremy Fitzhardinge , Andrew Morton , Rusty Russell , Zachary Amsden , Ian Pratt , Christian Limpach , Christoph Lameter List-Id: xen-devel@lists.xenproject.org On Tuesday 18 July 2006 11:56, Arjan van de Ven wrote: > On Tue, 2006-07-18 at 00:00 -0700, Chris Wright wrote: > > plain text document attachment (synch-ops) > > Add "always lock'd" implementations of set_bit, clear_bit and > > change_bit and the corresponding test_and_ functions. Also add > > "always lock'd" implementation of cmpxchg. These give guaranteed > > strong synchronisation and are required for non-SMP kernels running on > > an SMP hypervisor. > > Hi, > > this sounds really like the wrong approach; you know you're compiling > for xen, so why not just make set_bit() and the others use the lock'd > instructions at compile time? I guess because they only need it for a small subset of set_bits. -Andi