Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Aug 2004 11:59:49 -0700
From:      Nate Lawson <nate@root.org>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        current@freebsd.org
Subject:   Re: ACPI mpsafe patch for testing
Message-ID:  <411BBE25.3070404@root.org>
In-Reply-To: <20040812185649.GA30420@dhcp50.pn.xcllnt.net>
References:  <411BA70D.7010804@root.org> <20040812185649.GA30420@dhcp50.pn.xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?411BBE25.3070404>