From owner-freebsd-current@FreeBSD.ORG  Mon Apr  6 08:19:53 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C2BEA1065672
	for <current@freebsd.org>; Mon,  6 Apr 2009 08:19:53 +0000 (UTC)
	(envelope-from luigi@onelab2.iet.unipi.it)
Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129])
	by mx1.freebsd.org (Postfix) with ESMTP id 88F968FC1A
	for <current@freebsd.org>; Mon,  6 Apr 2009 08:19:53 +0000 (UTC)
	(envelope-from luigi@onelab2.iet.unipi.it)
Received: by onelab2.iet.unipi.it (Postfix, from userid 275)
	id 0DF90730A1; Mon,  6 Apr 2009 10:24:55 +0200 (CEST)
Date: Mon, 6 Apr 2009 10:24:55 +0200
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: current@freebsd.org
Message-ID: <20090406082455.GA3358@onelab2.iet.unipi.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Cc: 
Subject: stale CPU_DISABLE_CMPXCHG in atomic.h ?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 08:19:54 -0000

It seems to me that there is no reason to keep the
CPU_DISABLE_CMPXCHG option around in atomic.h -- the
only reason, mentioned in sys/i386/conf/NOTES, was
compatibility with old versions of VMware, long since fixed.

Any objections if i remove it ?

cheers
luigi