Date: Thu, 29 Apr 1999 14:01:05 -0400 (EDT) From: Luoqi Chen <luoqi@watermarkgroup.com> To: mike@smith.net.au Cc: darius@dons.net.au, freebsd-smp@FreeBSD.ORG, peter@netplex.com.au, tlambert@primenet.com Subject: Re: Really slow SMP Message-ID: <199904291801.OAA17851@lor.watermarkgroup.com>
next in thread | raw e-mail | index | archive | help
> > Maybe init_secondary() is too ealier for calling mem_range_AP_init, > > APs shouldn't be fooling around with locks at that point. I guess > > what happened was the AP was in a spin loop waiting for a lock and > > BSP timed out waiting for AP's up signal. Try move the call to ap_init() > > instead. > > 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. > > Regardless, Daniel, does that work for you? > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > 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. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904291801.OAA17851>