Do not held the kernel lock when calling hardclock() and statclock().

This is not necessary, as confirmed by tedu@ and kettenis@.

Solve the major contention problem seen on my Dual G5.  Reduce the
build time of a kernel with two jobs from 5h+ to 18min and expose more
easily pmap/memroy corruptions 8)

ok kettenis@

1 files changed, 1 insertions, 4 deletions

diff --git a/sys/arch/socppc/socppc/clock.c b/sys/arch/socppc/socppc/clock.c
index 4eba2210892..c1ebef574ef 100644
--- a/sys/arch/socppc/socppc/clock.c
+++ b/sys/arch/socppc/socppc/clock.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: clock.c,v 1.11 2014/10/08 10:12:41 mpi Exp $	*/
+/*	$OpenBSD: clock.c,v 1.12 2014/11/11 21:02:06 mpi Exp $	*/
 /*	$NetBSD: clock.c,v 1.1 1996/09/30 16:34:40 ws Exp $	*/
 
 /*
@@ -208,8 +208,6 @@ decr_intr(struct clockframe *frame)
 	if (ci->ci_cpl >= IPL_CLOCK) {
 		ci->ci_statspending += nstats;
 	} else {
-		KERNEL_LOCK();
-
 		nstats += ci->ci_statspending;
 		ci->ci_statspending = 0;
 
@@ -239,7 +237,6 @@ decr_intr(struct clockframe *frame)
 		/* if a tick has occurred while dealing with these,
 		 * dont service it now, delay until the next tick.
 		 */
-		KERNEL_UNLOCK();
 	}
 }