From owner-p4-projects@FreeBSD.ORG Tue Oct 19 22:19:08 2004 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 598A716A4D3; Tue, 19 Oct 2004 22:19:08 +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 12CF816A4CF; Tue, 19 Oct 2004 22:19:08 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5FD343D2D; Tue, 19 Oct 2004 22:19:07 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C73857A403; Tue, 19 Oct 2004 15:19:07 -0700 (PDT) Message-ID: <417592DB.6050609@elischer.org> Date: Tue, 19 Oct 2004 15:19:07 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: John Baldwin References: <200410192159.i9JLxNLE003024@repoman.freebsd.org> In-Reply-To: <200410192159.i9JLxNLE003024@repoman.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Perforce Change Reviews Subject: Re: 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 22:19:09 -0000 John Baldwin wrote: >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 > the implementation of IPIs or the implementation of IPIwakeup? > - 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 > >