Subject: Re: README: scheduler locking changes
To: None <thorpej@zembu.com>
From: James Chacon <jchacon@genuity.net>
List: current-users
Date: 08/20/2000 20:07:11
With these changes how close are we to "big-lock" testing on a wide basis?

i.e. something you're sure won't panic 10-15 minutes into a boot :-)

James


>
>On Sun, Aug 20, 2000 at 03:12:43PM -0700, Jason R Thorpe wrote:
>
> > PORT MASTERS: If I changed your port (m68k, mips, arm26, in particular)
> > please make sure the changes look sane.  Note, I had to change several
> > m68k ports Idle/cpu_switch implementations to look like the newer hp300
> > version.
>
>I forgot to mention...
>
>I did NOT change the following ports:
>
>	amigappc
>	arm32
>	bebox
>	evbsh3
>	macppc
>	mmeye
>	ofppc
>	pc532
>	prep
>	sparc
>	sparc64
>	vax
>
>These ports are BROKEN until port-masters update the port.  Note that
>the port may actually function, but a LOCKDEBUG kernel will panic on
>the first context switch.
>
>-- 
>        -- Jason R. Thorpe <thorpej@zembu.com>
>
>
>
>