linux-kernel - Re: [RFC PATCH] PCI MMCONFIG: add validation against ACPI motherboard resources

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: <4654AD91.1030808@pobox.com>
Date:	Wed, 23 May 2007 17:09:37 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Robert Hancock <hancockr@...w.ca>,
	Olivier Galibert <galibert@...ox.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...e.de>, Chuck Ebbert <cebbert@...hat.com>,
	Len Brown <lenb@...nel.org>
Subject: Re: [RFC PATCH] PCI MMCONFIG: add validation against ACPI motherboard
 resources

Jesse Barnes wrote:
> Apparently Vista will move away from using type 1 config space accesses 
> though, so if we keep using it, we'll probably run into some lame board 

Yep.

> that assumes you're using mmconfig at some point in the near future.  
> But then again, we're often on that less tested path (e.g. with ACPI), 
> so maybe that doesn't matter much.

One of the reasons why hardware vendors want to move away from 
traditional accesses is to be able to use the larger config space in 
PCI-Express, rather than being locked into the 256-byte legacy PCI 
config space.

Several modern PCI-Express devices utilize the upper config space, but 
due to legacy reasons the registers are usually ones that do not require 
OS drivers to know about (like BIST stuff or diagnostic registers).

Expect that to change, as MS shakes out the bugs (or maybe we are doing 
their job for them?).

	Jeff

-
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/