linux-kernel - Re: SNB PCI root information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQVzKr+nyBh=8-v+HEDF=7JqN2CqdTNx1=LHTq=c_OyZvg@mail.gmail.com>
Date:	Mon, 18 Jun 2012 16:40:42 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Ulrich Drepper <drepper@...il.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.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 Mon, Jun 18, 2012 at 3:30 PM, Ulrich Drepper <drepper@...il.com> wrote:
> On Sat, Jun 16, 2012 at 5:56 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> If ACPI provides a perfectly usable generic way to describe this
>> topology and the vendor BIOS doesn't bother to use it, I'm not very
>> interested in trying to compensate for that BIOS deficiency by adding
>> a bunch of non-portable CPU-specific gunk to Linux.
>
> The problem is that all machines get this wrong.  I've tested varies
> models from Dell and HP and none of them have the _PXM entry and the
> local_cpus fields are wrong.  If there is a reasonably sane way to
> compensate for broken BIOSes it should be considered.  We all know how
> good BIOS authors are...

please check attached one. and  you may append "pci=busnum_node=00:00,80:01"
to change node for root bus.
assume you have two root bus: 00, 80

Thanks

Yinghai

Download attachment "busnum_node.patch" of type "application/octet-stream" (1604 bytes)