Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755282AbaDXJlX (ORCPT ); Thu, 24 Apr 2014 05:41:23 -0400 Received: from mail-oa0-f49.google.com ([209.85.219.49]:51590 "EHLO mail-oa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755129AbaDXJlS (ORCPT ); Thu, 24 Apr 2014 05:41:18 -0400 MIME-Version: 1.0 In-Reply-To: <20140424072021.GA3396@gmail.com> References: <20140421221721.26308.1891.stgit@bhelgaas-glaptop.roam.corp.google.com> <20140424072021.GA3396@gmail.com> Date: Thu, 24 Apr 2014 11:41:17 +0200 Message-ID: Subject: Re: [PATCH 2] PNP: Work around BIOS defects in Intel MCH area reporting From: Stephane Eranian To: Ingo Molnar Cc: Bjorn Helgaas , "Rafael J. Wysocki" , Aaron Lu , Linux PCI , x86 , LKML , ACPI Devel Maling List , Borislav Petkov , "H. Peter Anvin" , Zheng Z Yan , Dave Jones , Rui Zhang , Yinghai Lu 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 Thu, Apr 24, 2014 at 9:20 AM, Ingo Molnar wrote: > > * Stephane Eranian wrote: > >> On Tue, Apr 22, 2014 at 12:17 AM, Bjorn Helgaas wrote: >> > Work around BIOSes that don't report the entire Intel MCH area. >> > >> > MCHBAR is not an architected PCI BAR, so MCH space is usually reported as a >> > PNP0C02 resource. The MCH space was once 16KB, but is 32KB in newer parts. >> > Some BIOSes still report a PNP0C02 resource that is only 16KB, which means >> > the rest of the MCH space is consumed but unreported. >> > >> > This can cause resource map sanity check warnings or (theoretically) a >> > device conflict if we assigned the unreported space to another device. >> > >> > The Intel perf event uncore driver tripped over this when it claimed the >> > MCH region: >> > >> > resource map sanity check conflict: 0xfed10000 0xfed15fff 0xfed10000 0xfed13fff pnp 00:01 >> > Info: mapping multiple BARs. Your kernel is fine. >> > >> > To prevent this, if we find a PNP0C02 resource that covers part of the MCH >> > space, extend it to cover the entire space. >> > >> Works for me on my Levono IvyBridge laptop. >> Thanks for fixing this, Bjorn. >> Acked-by: Stephane Eranian > > Just curious, what problems triggered on your laptop: only the > warnings, or did something get mapped to the undeclared area, > causing other misbehavor? > In my case, it was just the warning. Everything appeared to worked correctly. -- 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/