Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753581Ab2FSSUN (ORCPT ); Tue, 19 Jun 2012 14:20:13 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:41787 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753064Ab2FSSUL convert rfc822-to-8bit (ORCPT ); Tue, 19 Jun 2012 14:20:11 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 19 Jun 2012 11:20:10 -0700 X-Google-Sender-Auth: TurrBXwr0ZdSUgxGdDaMowEqH8Q Message-ID: Subject: Re: SNB PCI root information From: Yinghai Lu To: Bjorn Helgaas Cc: Ulrich Drepper , jbarnes@virtuousgeek.org, Linux Kernel Mailing List , lenb@kernel.org, x86@kernel.org, linux-pci@vger.kernel.org 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: 1023 Lines: 24 On Tue, Jun 19, 2012 at 5:36 AM, Bjorn Helgaas wrote: > > I'm not opposed to something like this, if people think it's useful. > > This patch sets the node quite early, before we even look at the _PXM > information in pci_acpi_scan_root(). ?That means if the BIOS does > supply a _PXM method and the user gives this argument, the > user-supplied info is silently overwritten. ?To me it would make more > sense to handle an option like this *after* we look for _PXM info. > That way it could be used to compensate for both missing and incorrect > _PXM info. yes, we can only let user input and hostbridge touch that array. but i'd like to only handle missing _PXM case. If the BIOS provide wrong _PXM, that BIOS really should be fixed at first. Yinghai -- 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/