From owner-freebsd-current@FreeBSD.ORG Tue Feb 28 15:22:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17BD910656B3; Tue, 28 Feb 2012 15:22:58 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id BDF368FC1F; Tue, 28 Feb 2012 15:22:57 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id q1SFMpHY027218; Tue, 28 Feb 2012 08:22:51 -0700 (MST) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=iso-8859-1 From: Scott Long In-Reply-To: <201202280844.22142.jhb@freebsd.org> Date: Tue, 28 Feb 2012 08:22:51 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <22F18CA9-4C58-446D-892B-28B67E343CE2@samsco.org> References: <4F26CC5A.2070501@FreeBSD.org> <4F4B5ED3.5090508@FreeBSD.org> <65B1891F-9079-4948-BF37-8A50B4E85071@samsco.org> <201202280844.22142.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1257) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: revisiting tunables under Safe Mode menu option X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2012 15:22:58 -0000 On Feb 28, 2012, at 6:44 AM, John Baldwin wrote: > On Monday, February 27, 2012 2:03:21 pm Scott Long wrote: >>=20 >> On Feb 27, 2012, at 3:45 AM, Andriy Gapon wrote: >>=20 >>> on 30/01/2012 18:59 Andriy Gapon said the following: >>>>=20 >>>> First, I think that this proposal/discussion could have been more = useful before >>>> the 9.0. Maybe the RE would be interested in adding another item = to their >>>> pre-release checklist: ask developers about what could be dropped = and what should >>>> be added to the Safe Mode settings in a new (.0) release. Probably = the developers >>>> should keep the Safe Mode in mind too when adding new features or = making other >>>> drastic changes, but the reminder should be welcome. >>> [snip] >>>> o Since we have a separate ACPI option and because ACPI now is = almost a mandatory >>>> thing (and not a significant source of boot troubles), maybe we = could remove the >>>> code that automatically disables ACPI in Safe Mode? >>>>=20 >>>> o hint.apic.0.disabled - APIC code doesn't seem to be a significant = source of boot >>>> troubles, like ACPI it has become almost a mandatory thing. So = maybe we should >>>> remove this setting? >>=20 >> Turning off the APIC turns off SMP in a very efficient, clean manner. = I added this not to isolate the APIC code, but to turn off SMP. That's = why=20 > it's there, and I'd like the ability to turn off SMP to stay there in = some form. If there's a better way to disable SMP that doesn't get into=20= > problems with interrupt delivery, then please propose it. As for it = being mandatory, it's really only mandatory for MSI these days, though = it used=20 > to be required for more complex PCIX topologies. >=20 > You want APIC for other things as well (hwpmc(4) requires it, as do = CMCI > interrupts, and we really do like to make use of the local APIC = timer). >=20 Well, 'Safe Mode' isn't meant to be a normal, continuous operating mode, = it's meant to be a debug mode that helps boot otherwise unbeatable = systems. Scott