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]

Date:	Mon, 18 Jun 2012 18:30:21 -0400
From:	Ulrich Drepper <drepper@...il.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Yinghai Lu <yinghai@...nel.org>, 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 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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/