Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261413AbVA1O3S (ORCPT ); Fri, 28 Jan 2005 09:29:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261410AbVA1O2o (ORCPT ); Fri, 28 Jan 2005 09:28:44 -0500 Received: from bay-bridge.veritas.com ([143.127.3.10]:53835 "EHLO MTVMIME01.enterprise.veritas.com") by vger.kernel.org with ESMTP id S261413AbVA1O2X (ORCPT ); Fri, 28 Jan 2005 09:28:23 -0500 Date: Fri, 28 Jan 2005 14:27:51 +0000 (GMT) From: Hugh Dickins X-X-Sender: hugh@goblin.wat.veritas.com To: Andi Kleen cc: akpm@osdl.org, linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net Subject: Re: [PATCH] Add CONFIG_X86_APIC_OFF for i386/UP In-Reply-To: <20050128133927.GC6703@wotan.suse.de> Message-ID: References: <20050128133927.GC6703@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1026 Lines: 24 On Fri, 28 Jan 2005, Andi Kleen wrote: > > This patch adds a new CONFIG_X86_APIC_OFF option. This is useful > for distribution UP kernels who should run with local APIC off by > default (because older machines often have broken mptables etc.). > > But there are a few machines who don't boot with apic off so there > needs to be an command line option to enable it. > > When X86_APIC_OFF is set the APIC code is compiled in, but is > only enabled when "apic" or "lapic" is specified on the command line > (or a DMI scanner force enables it). I'm confused! Why do we need X86_APIC_OFF config option (but code compiled in), with boot options "apic" or "lapic" to enable it, when we already have the code compiled in, with boot options "noapic" or "nolapic" to disable it? Hugh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/