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: <CAE9FiQVDnS9n28GQrKVVTU7GiMtJZLFN1T9vmOm5oSysvMEVhQ@mail.gmail.com>
Date:	Tue, 19 Jun 2012 11:20:10 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	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 Tue, Jun 19, 2012 at 5:36 AM, Bjorn Helgaas <bhelgaas@...gle.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/