From owner-freebsd-current@FreeBSD.ORG  Sun Aug 22 19:05:39 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6BB9016A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 22 Aug 2004 19:05:39 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3AAB743D41
	for <freebsd-current@freebsd.org>;
	Sun, 22 Aug 2004 19:05:39 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 31D1C72DD4; Sun, 22 Aug 2004 12:05:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 2CA2572DCB
	for <freebsd-current@freebsd.org>;
	Sun, 22 Aug 2004 12:05:39 -0700 (PDT)
Date: Sun, 22 Aug 2004 12:05:39 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: freebsd-current@freebsd.org
Message-ID: <20040822115345.Y94593@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: PLEASE TEST: IPI deadlock avoidance patch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Sun, 22 Aug 2004 19:05:39 -0000

Hey folks,

If you have a reasonably fast i386 or amd64 multiprocessor and/or
hyperthreading machine and are experiencing reproducible hangs during -j
buildwords and other highly parallel operations, please try this patch:

http://people.freebsd.org/~dwhite/smp_rv_mtx.patch

This patch avoids a deadlock between the smp_rendezvous() mechanism and
TLB shootdowns via pmap by forcing them to share a mutex.  The patch has
been tested on several multiproc Xeon systems and a dual Opteron I have
here and is stable, but a couple of more eyeballs and varied loads
wouldn't hurt since this will be going into RELENG_5.

If there's anything glaringly wrong from a style point of view, let me
know too.

I plan on committing this late Monday or Tuesday, barring any serious
problems.

Thanks to alc for the nudge on the solution and rwatson for staying up
late and testing it on his hardware.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org