From owner-p4-projects@FreeBSD.ORG Tue Oct 19 21:59:24 2004 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 5CAE916A4D0; Tue, 19 Oct 2004 21:59:24 +0000 (GMT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1290116A4CE for ; Tue, 19 Oct 2004 21:59:24 +0000 (GMT) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0940543D1F for ; Tue, 19 Oct 2004 21:59:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.11/8.12.11) with ESMTP id i9JLxNit003027 for ; Tue, 19 Oct 2004 21:59:23 GMT (envelope-from jhb@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.11/8.12.11/Submit) id i9JLxNLE003024 for perforce@freebsd.org; Tue, 19 Oct 2004 21:59:23 GMT (envelope-from jhb@freebsd.org) Date: Tue, 19 Oct 2004 21:59:23 GMT Message-Id: <200410192159.i9JLxNLE003024@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to jhb@freebsd.org using -f From: John Baldwin To: Perforce Change Reviews Subject: PERFORCE change 63396 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 21:59:25 -0000 http://perforce.freebsd.org/chv.cgi?CH=63396 Change 63396 by jhb@jhb_tibook on 2004/10/19 21:58:24 Update. Affected files ... .. //depot/projects/smpng/sys/notes#21 edit Differences ... ==== //depot/projects/smpng/sys/notes#21 (text+ko) ==== @@ -33,6 +33,10 @@ - Untested - Don't allow kthreads to get signalled and do bad things - Untested +- Change amd64 to use [ls]fence instructions for memory barriers. + - Untested (and no hardware, maybe peter can test) +- Turn off the ipiwakeups in 4BSD since the currently implementation can + lead to IPI deadlocks - Add a kproc API that does what kthread does right now - Add a real kthread API that creates just another thread inside of a kproc - Figure out what needs to be done to make a new kthread.. should each