Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758018Ab2FTT5d (ORCPT ); Wed, 20 Jun 2012 15:57:33 -0400 Received: from mail4-relais-sop.national.inria.fr ([192.134.164.105]:28309 "EHLO mail4-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754452Ab2FTT5b (ORCPT ); Wed, 20 Jun 2012 15:57:31 -0400 X-IronPort-AV: E=Sophos;i="4.77,446,1336341600"; d="scan'208";a="148281948" Message-ID: <4FE22B28.9020402@gmail.com> Date: Wed, 20 Jun 2012 21:57:28 +0200 From: Brice Goglin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4 MIME-Version: 1.0 To: Yinghai Lu CC: Bjorn Helgaas , Ulrich Drepper , jbarnes@virtuousgeek.org, Linux Kernel Mailing List , lenb@kernel.org, x86@kernel.org, linux-pci@vger.kernel.org Subject: Re: SNB PCI root information References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1187 Lines: 27 Le 20/06/2012 21:28, Yinghai Lu a ?crit : > On Wed, Jun 20, 2012 at 11:46 AM, Bjorn Helgaas wrote: > >> As far as I can tell, here's Yinghai's recommendation: the user >> argument should not override BIOS _PXM because if the BIOS gets the >> _PXM wrong, the user won't be able to work around it with the >> argument, which will force the vendor to fix the BIOS. >> >> I'm not buying it. The convention that user-supplied arguments always >> take precedence is useful, easy to document, and matches user >> expectations. It allows the user to work around both missing _PXM and >> incorrect _PXM. > if the vendor provide _PXM, that _PXM should be right and be trusted. > I agree that the most common problem is that _PXM is missing. But I've seen at least some HP Westmere-EP platforms where _PXM exists but it is wrong. Last time we checked, there was no BIOS update, even if we reported the bug a while ago. Brice -- 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/