From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757223AbbCDNwd (ORCPT ); Wed, 4 Mar 2015 08:52:33 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:62501 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753254AbbCDNwc (ORCPT ); Wed, 4 Mar 2015 08:52:32 -0500 From: "Rafael J. Wysocki" To: Borislav Petkov Cc: Arjan van de Ven , Ingo Molnar , "Li, Aubrey" , "alan@linux.intel.com" , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Len.Brown@intel.com, x86@kernel.org, LKML Subject: Re: [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced platform Date: Wed, 04 Mar 2015 15:16:07 +0100 Message-ID: <8773039.WD3UIoUtJl@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.19.0+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20150304095011.GH3233@pd.tnic> References: <54F67ACC.3010500@linux.intel.com> <54F6C59C.706@linux.intel.com> <20150304095011.GH3233@pd.tnic> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, March 04, 2015 10:50:11 AM Borislav Petkov wrote: > On Wed, Mar 04, 2015 at 12:43:08AM -0800, Arjan van de Ven wrote: > > > > > >Using 'acpi_gbl_reduced_hardware' flag outside the ACPI code > > >is a mistake. > > > > ideally, the presence of that flag in the firmware table will clear/set more global settings, > > for example, having that flag should cause the 8042 input code to not probe for the 8042. > > > > for interrupts, there really ought to be a "apic first/only" mode, which is then used on > > all modern systems (not just hw reduced). > > Do we need some sort of platform-specific querying interfaces now too, > similar to cpu_has()? I.e., platform_has()... > > if (platform_has(X86_PLATFORM_REDUCED_HW)) > do stuff.. > > Hmmm. Sort of. What we need is a "do not touch PIC/PIT" bit for the code that tries to fall back to them in some cases (which may appear to work if the hardware is physically there, but it may confuse the platform). -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.