From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756836AbYFRWdT (ORCPT ); Wed, 18 Jun 2008 18:33:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755190AbYFRWdA (ORCPT ); Wed, 18 Jun 2008 18:33:00 -0400 Received: from rv-out-0506.google.com ([209.85.198.238]:12698 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754868AbYFRWc7 (ORCPT ); Wed, 18 Jun 2008 18:32:59 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pbd6JESas28sRBYCXycHNhk2pS2Rqm0SPCmrVhpphLBzU5SyEssEFrYdiyMVQ91opf s+3VNSSbIj4c3Qra+GMI+2YZNmrq1ql2yRH9Bq1vI133BToytua8kqgpR5poqWDoNBFs 5RQbsG6BngHZIoTJ+mhWXozQZakbK7IzAsyXQ= Message-ID: <86802c440806181532g348864e1u3d067f8366046a7f@mail.gmail.com> Date: Wed, 18 Jun 2008 15:32:59 -0700 From: "Yinghai Lu" To: "Len Brown" Subject: Re: [PATCH] x86: update mptable v7 Cc: "Ingo Molnar" , "Thomas Gleixner" , "H. Peter Anvin" , "Andrew Morton" , "Eric W. Biederman" , "linux-kernel@vger.kernel.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200805041823.57198.yhlu.kernel@gmail.com> <200805191252.36814.yhlu.kernel@gmail.com> <200805251600.26325.yhlu.kernel@gmail.com> <200806011317.38622.yhlu.kernel@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 18, 2008 at 3:18 PM, Len Brown wrote: > > > On Sun, 1 Jun 2008, Yinghai Lu wrote: > >> >> make mptable to be consistent to acpi routing, so we could >> 1. kexec kernel with acpi=off >> 2. workaround BIOS that acpi routing is working, but mptable is not right. >> so can use kernel/kexec to start other os that doesn't have good acpi support > > Is this an effort to boot an ACPI-mode kernel, > and then kexec a non-ACPI kernel? Yes, > > Doing so could confuse the heck out of the platform firmware, > which will think that an ACPI-mode kernel is still running. > > Note that it is a historic artifact, now considered a bug, > that ACPI uses the MPS code. We should be divorcing these > two bodies of code rather than mixing them further. how about adding config option to not compile mptable related info? YH