From owner-cvs-all@FreeBSD.ORG Tue Mar 27 19:04:13 2007 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 666BA16A400; Tue, 27 Mar 2007 19:04:13 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 37AC613C4B0; Tue, 27 Mar 2007 19:04:13 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 261881A3C1C; Tue, 27 Mar 2007 12:04:13 -0700 (PDT) Date: Tue, 27 Mar 2007 12:04:13 -0700 From: Alfred Perlstein To: Marcel Moolenaar Message-ID: <20070327190413.GN68915@elvis.mu.org> References: <200703270529.l2R5TfVk087238@repoman.freebsd.org> <20070327074334.GA52121@xor.obsecurity.org> <2EA36547-0EB1-47B0-8F07-D394394CF3BD@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2EA36547-0EB1-47B0-8F07-D394394CF3BD@mac.com> User-Agent: Mutt/1.4.2.2i Cc: cvs-src@FreeBSD.org, Marcel Moolenaar , cvs-all@FreeBSD.org, src-committers@FreeBSD.org, Kris Kennaway Subject: Re: cvs commit: src/sys/kern vfs_subr.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2007 19:04:13 -0000 I'm not sure if it helps, but I recall that PPC memory barriers were pretty much useless except the strongest ones. * Marcel Moolenaar [070327 09:38] wrote: > > On Mar 27, 2007, at 12:43 AM, Kris Kennaway wrote: > > >On Tue, Mar 27, 2007 at 05:29:41AM +0000, Marcel Moolenaar wrote: > >>marcel 2007-03-27 05:29:41 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> sys/kern vfs_subr.c > >> Log: > >> PowerPC is the only architecture with mpsafe_vfs=0. This is now > >> broken. Rudimentary tests show that PowerPC can run with > >> mpsafe_vfs=1. Make it so... > > > >If this is the vget panic via soft updates then a fix is pending for > >that. Nevertheless mpsafevfs=1 is a good thing :) > > Maybe. I don't have the backtrace handy. It had to do with S/U, so it > probably is then. I didn't see it on my amd64 box, so I assumed it was > specific to PowerPC. Setting mpsave_vfs=1 solved it for me (or > should I say avoided it for me? :-) I figured it's better to hunt down > bugs in the mpsafe_vfs=1 case then it is in the mpsafe_vfs=0 case. > This is not to say that mpsafe_vfs=0 can be broken, but rather that > I prefer to work on improving the mpsafe_vfs=1 case... > > Hmmm, maybe I don't have S/U on amd64 box (I don't bother to partition > my development boxes, so I typically only have a / mount that has S/U. > Everything is basically over NFS...) > > -- > Marcel Moolenaar > xcllnt@mac.com > -- - Alfred Perlstein, RED Incorporated Consulting. - coder / sysadmin / FreeBSD Hacker / All that jazz -