From owner-freebsd-smp  Fri Apr 30  2:34:44 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33])
	by hub.freebsd.org (Postfix) with ESMTP id F345D15906
	for <freebsd-smp@freebsd.org>; Fri, 30 Apr 1999 02:34:37 -0700 (PDT)
	(envelope-from magnus@ludd.luth.se)
Received: from speedy.ludd.luth.se (root@speedy.ludd.luth.se [130.240.16.164])
	by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id LAA22692;
	Fri, 30 Apr 1999 11:34:32 +0200
From: Magnus Gr|nlund <magnus@ludd.luth.se>
Received: (magnus@localhost) by speedy.ludd.luth.se (8.8.8/8.6.11) id LAA25670; Fri, 30 Apr 1999 11:34:31 +0200 (CEST)
Message-Id: <199904300934.LAA25670@speedy.ludd.luth.se>
Subject: Re: Really slow SMP
In-Reply-To: <199904292131.OAA00867@dingo.cdrom.com> from Mike Smith at "Apr 29, 99 02:31:38 pm"
To: mike@smith.net.au (Mike Smith)
Date: Fri, 30 Apr 1999 11:34:31 +0200 (CEST)
Cc: freebsd-smp@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > > 
> > > Sorry, not sure I follow you here; there's no locking in 
> > > mem_range_AP_init(), and it's where the MTRRs were being loaded before. 
> > > The code path is a little more convoluted now, but has the same basic 
> > > effect.
> >
> > IIRC, disable_intr() for SMP needs to get a lock to prevent intr from
> > occuring on all cpus. In any case, it's safer to do it ap_init() when
> > the AP holds the giant lock.
> 
> Point.  Here's a new diff; can the people with "slow SMP" problems try 
> this one?
> 

I got the "slow SMP"-problem and applying the patches to yesterdays current
resulted in "general protection fault in kernel mode" when
mem_range_AP_init() is called. 

/Magnus


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message