Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932584AbWHCRQr (ORCPT ); Thu, 3 Aug 2006 13:16:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932585AbWHCRQr (ORCPT ); Thu, 3 Aug 2006 13:16:47 -0400 Received: from 216-99-217-87.dsl.aracnet.com ([216.99.217.87]:56963 "EHLO sous-sol.org") by vger.kernel.org with ESMTP id S932584AbWHCRQq (ORCPT ); Thu, 3 Aug 2006 13:16:46 -0400 Date: Thu, 3 Aug 2006 10:18:06 -0700 From: Chris Wright To: Christoph Lameter Cc: Andi Kleen , virtualization@lists.osdl.org, Jeremy Fitzhardinge , akpm@osdl.org, xen-devel@lists.xensource.com, Chris Wright , Ian Pratt , linux-kernel@vger.kernel.org Subject: Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor. Message-ID: <20060803171806.GB2654@sequoia.sous-sol.org> References: <20060803002510.634721860@xensource.com> <200608030739.13334.ak@suse.de> <200608030802.44391.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 734 Lines: 16 * Christoph Lameter (clameter@sgi.com) wrote: > An include would need to fall back to asm-generic if > there is no file in asm-arch/xen-bitops.h. I thought we had such a > mechanism? While Xen is the primary user, it is a misnomer to call it xen-bitops. These are simply always locked, hence the sync-bitops name. Also, there's a use of sync_cmpxchg, and cmpxchg is not in bitops.h. As for the mechanism, it is manual. Arch specific header includes asm-generic one. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/