From owner-freebsd-acpi@FreeBSD.ORG Thu Aug 12 18:59:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6404C16A4CF; Thu, 12 Aug 2004 18:59:52 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3613543D53; Thu, 12 Aug 2004 18:59:52 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7CIxp8U030813; Thu, 12 Aug 2004 11:59:51 -0700 Message-ID: <411BBE25.3070404@root.org> Date: Thu, 12 Aug 2004 11:59:49 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcel Moolenaar References: <411BA70D.7010804@root.org> <20040812185649.GA30420@dhcp50.pn.xcllnt.net> In-Reply-To: <20040812185649.GA30420@dhcp50.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI mpsafe patch for testing X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 18:59:52 -0000 Marcel Moolenaar wrote: > On Thu, Aug 12, 2004 at 10:21:17AM -0700, Nate Lawson wrote: > >>I plan to commit the mpsafe patch for acpi on Friday morning. No >>problems so far for testers and I've run it for weeks (versions of it >>for months). The only change I've made is to update it against commits >>so it will apply cleanly. >> >>Please test if you get a chance. Again the URL: >>http://root.org/~nate/freebsd/acpi_mpsafe.diff.gz > > > ia64: pluto1.freebsd.org is running with the patch. I also performed > a reboot without problems. > > Note that pluto1 runs an UP kernel. Are there any SMP specific MD > code paths you think I should test or is it sufficient that SMP is > tested on i386 (or amd64)? For ia64, I was most concerned about alignment issues. So anything (UP or SMP) that exercises code paths is helpful. The only SMP-specific things to test are power-off on shutdown. Run it a bunch of times to be sure that it continues to work. Note this isn't in the acpi locking path but ACPI-CA has its own locks which are now not redundantly covered by Giant. It has been running this way in Linux for a year or so. Still, it's good to have that test coverage too. -- Nate