[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQWKxe9VYvrQy5h4RP2dS7YHHXu4icjC+KPipkRKbsZN1g@mail.gmail.com>
Date: Wed, 20 Jun 2012 20:50:03 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Ulrich Drepper <drepper@...il.com>, jbarnes@...tuousgeek.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
lenb@...nel.org, x86@...nel.org, linux-pci@...r.kernel.org
Subject: Re: SNB PCI root information
On Wed, Jun 20, 2012 at 7:37 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Wed, Jun 20, 2012 at 12:34 PM, Ingo Molnar <mingo@...nel.org> wrote:
>>> if the vendor provide _PXM, that _PXM should be right and be
>>> trusted.
>>>
>>> if the vendor does not provide _PXM, we can have command line
>>> to input it before user can get one updated BIOS from vendor.
>>
>> So how about an incorrect _PXM, or a slightly inefficient one?
>> Why shouldn't it be possible for the user to override it?
>
> Try to keep the code simple.
>
>>
>> I mean, if we create a parameter space that tweaks data then why
>> not make it complete and allow *all* firmware data to be
>> (optionally) modified, from the kernel boot line?
>
> that pxm/node for pci device should be consistent with srat table etc,
> so better solution is that BIOS keep them consistent.
>
> If BIOS provide _PXM for pci device, the _PXM should have more chance
> to be right.
>
> Anyway if you insist that it should cover that wrong case, let me
> check if it could be done simply.
please check -v3, and it will add 40 lines.
and -v2 is about 25 lines.
Thanks
Yinghai
Download attachment "busnum_node_v3.patch" of type "application/octet-stream" (3956 bytes)
Powered by blists - more mailing lists