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: <CAE9FiQWOUZhUQYc66ceG5EMWQ0uO7L3odh0+XwRsLV2Bza2ZpQ@mail.gmail.com>
Date:	Wed, 20 Jun 2012 12:28:12 -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 Wed, Jun 20, 2012 at 11:46 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:

> As far as I can tell, here's Yinghai's recommendation:  the user
> argument should not override BIOS _PXM because if the BIOS gets the
> _PXM wrong, the user won't be able to work around it with the
> argument, which will force the vendor to fix the BIOS.
>
> I'm not buying it.  The convention that user-supplied arguments always
> take precedence is useful, easy to document, and matches user
> expectations.  It allows the user to work around both missing _PXM and
> incorrect _PXM.

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.

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/