linux-kernel - Re: [PATCH] Documentation: Explain pci=conf1,conf2 more verbosely

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: <20160114132716.761edc01@lwn.net>
Date:	Thu, 14 Jan 2016 13:27:16 -0700
From:	Jonathan Corbet <corbet@....net>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Eric Morton <Eric.Morton@....com>, linux-doc@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: Explain pci=conf1,conf2 more verbosely

On Wed, 13 Jan 2016 16:48:51 +0100
Borislav Petkov <bp@...en8.de> wrote:

> People complained that setting the PCI config space access mechanism
> through "pci=conf1" or "pci=conf2" on the command line is not really
> documented. Yeah, can you blame them? Look at what we have now.
> 
> So try to improve the situation a bit by explaining what those "conf1"
> and "conf2" things actually mean.

Seems good, applied to the docs tree...

> See http://wiki.osdev.org/PCI for more info.

...but I took the liberty of adding this URL too; people reading the
document are unlikely to check the commit log in case there's a useful
pointer waiting there for them :)

Thanks,

jon