Date: Tue, 28 Feb 2012 14:18:16 -0800 From: Kevin Oberman <kob6558@gmail.com> To: Scott Long <scottl@samsco.org> Cc: FreeBSD current <freebsd-current@freebsd.org>, Devin Teske <dteske@vicor.com>, Andriy Gapon <avg@freebsd.org> Subject: Re: revisiting tunables under Safe Mode menu option Message-ID: <CAN6yY1s%2BOfTZjjWMmPm5WzVfB7O_CaJc7th_qLZ8Ej1FhBA7=w@mail.gmail.com> In-Reply-To: <3BA1B476-ED05-4E8E-8DFA-0B06EFB48867@samsco.org> References: <4F26CC5A.2070501@FreeBSD.org> <4F4B5ED3.5090508@FreeBSD.org> <65B1891F-9079-4948-BF37-8A50B4E85071@samsco.org> <4F4C0600.2000903@FreeBSD.org> <3BA1B476-ED05-4E8E-8DFA-0B06EFB48867@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 27, 2012 at 10:23 PM, Scott Long <scottl@samsco.org> wrote: > > On Feb 27, 2012, at 3:38 PM, Andriy Gapon wrote: >>> >>> Turning off the APIC turns off SMP in a very efficient, clean manner. = =A0I >>> added this not to isolate the APIC code, but to turn off SMP. =A0That's= why >>> it's there, and I'd like the ability to turn off SMP to stay there in s= ome >>> form. >> >> I think that this is a good idea. >> >>> If there's a better way to disable SMP that doesn't get into problems >>> with interrupt delivery, then please propose it. >> >> I think that kern.smp.disabled should be it. >> > > I recall this tunable being problematic, but I don't recall the reason. = =A0Reading the code > makes me think that it should be fine; maybe it's time to switch this kno= b from > hint.apic.0.disabled to kern.smp.disabled, as you've done in your propose= d patch. APIC is required for SMP, but works on many older, single CPU systems and removes the massive sharing of IRQs common on non-APIC systems. OTOH, some ThinkPads simply won't boot with APIC. My old T43 (Pentium-M) had this issue. I had to turn off APIC to get a GENERIC kernel to boot. I think that I have heard of other systems that have an issue with FreeBSD APIC. (APIC seems to work fine with Windows, so it's something about the FreeBSD implementation, but the problem is pretty rare, seems limited to 3-5 year old uniprocessor systems, so it's probably not worth trying to track down. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1s%2BOfTZjjWMmPm5WzVfB7O_CaJc7th_qLZ8Ej1FhBA7=w>