From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754594AbaDPGv4 (ORCPT ); Wed, 16 Apr 2014 02:51:56 -0400 Received: from mail-ee0-f41.google.com ([74.125.83.41]:41061 "EHLO mail-ee0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751601AbaDPGvy (ORCPT ); Wed, 16 Apr 2014 02:51:54 -0400 Date: Wed, 16 Apr 2014 08:51:48 +0200 From: Ingo Molnar To: Feng Tang Cc: Clemens Ladisch , tglx@linutronix.de, mingo@elte.hu, hpa@zytor.com, linux-kernel@vger.kernel.org, John Stultz , Andy Lutomirski Subject: Re: [PATCH v2] x86: hpet: Don't default CONFIG_HPET_TIMER to be y for X86_64 Message-ID: <20140416065148.GB1193@gmail.com> References: <1395975316-4795-1-git-send-email-feng.tang@intel.com> <20140328071716.GC30107@gmail.com> <20140328073718.GA12762@feng-snb> <53352DE5.2090600@ladisch.de> <20140328081117.GA32308@gmail.com> <20140415074443.GA10911@feng-snb> <20140415090025.GA31244@gmail.com> <20140415095539.GA19271@feng-snb> <20140415104206.GA31656@gmail.com> <20140415141206.GA12076@feng-snb> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140415141206.GA12076@feng-snb> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Feng Tang wrote: > On Tue, Apr 15, 2014 at 12:42:06PM +0200, Ingo Molnar wrote: > > > > * Feng Tang wrote: > > > > > On Tue, Apr 15, 2014 at 11:00:25AM +0200, Ingo Molnar wrote: > > > > > > > > * Feng Tang wrote: > > > > > > > > > Hi Ingo, > > > > > > > > > > On Fri, Mar 28, 2014 at 09:11:17AM +0100, Ingo Molnar wrote: > > > > > > > > > > > > * Clemens Ladisch wrote: > > > > > > > > > > > > > Feng Tang wrote: > > > > > > > > On Fri, Mar 28, 2014 at 08:17:16AM +0100, Ingo Molnar wrote: > > > > > > > >> * Feng Tang wrote: > > > > > > > >> - or the kernel should have a quirk to reliably disable it. Why > > > > > > > >> should we crash or misbehave if a driver is built into the > > > > > > > >> kernel? > > > > > > > > > > > > > > > > I thought about this before, HPET doesn't have PCI ID like stuff, > > > > > > > > > > > > > > HPET does have the PCI vendor ID in the first register. > > > > > > > > > > > > > > > only thing I can think of to identify them may be the CPU family/ID. > > > > > > > > > > > > > > The HPET is implemented by some actual chip, and that chip also has lots > > > > > > > of PCI devices. (In the case of a SoC, the CPU ID would work, too). > > > > > > > > > > > > Correct. See arch/x86/kernel/hpet.c, which has a large number of HPET > > > > > > quirks keyed off chipset PCI IDs: > > > > > > > > > > > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ESB2_0, > > > > > > ich_force_enable_hpet); > > > > > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_0, > > > > > > ich_force_enable_hpet); > > > > > > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH6_1, > > > > > > ich_force_enable_hpet); > > > > > > [...] > > > > > > > > > > I just gave it another thought, that the HPET on our platform > > > > > currently do have some problem to be used as clocksource/clockevent, > > > > > but it may get fixed in future version (by Silicon or BIOS). > > > > > > > > > > If I add quirk to block it now, I may revert this code in future > > > > > when it get fixed, same problem applis for the future generation of > > > > > platform. > > > > > > > > If the hardware or BIOS gets fixed then that will be visible in the > > > > revision level of the hardware, right? > > > > > > AFAIK, if it is fixed in a new silicon version, we should be able to > > > detect it by the "stepping", but the PCI DEV ID is not likely to > > > change. > > > > > > If it is fixed by BIOS or PUNIT FW, then we may go through the > > > DMI info to check the BIOS version, One problem is there is some > > > Baytrail tablet platforms that doesn't provide DMI info as its > > > FW is not UEFI/Legacy BIOS compatible version. > > > > So just turn it off for the current hardware, via PCI ID. When you > > get a fix, you can turn it back on again by refining the quirk > > check, for that specific hardware. > > got it, thanks! Btw., note that such narrow quirk refinings are pretty uncontroversial and have a pretty fast path upstream, once you have the initial quirk in there. Thanks, Ingo