linux-kernel - Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in

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: <1198874556.7209.38.camel@pasglop>
Date:	Sat, 29 Dec 2007 07:42:36 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Loic Prylli <loic@...i.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Robert Hancock <hancockr@...w.ca>,
	Jeff Garzik <jeff@...zik.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	gregkh@...e.de, linux-pci <linux-pci@...ey.karlin.mff.cuni.cz>,
	Martin Mares <mj@....cz>, Matthew Wilcox <matthew@....cx>,
	Kai Ruhnau <kai@...getaschen.dyndns.org>
Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver
	opt-in


On Fri, 2007-12-28 at 14:14 -0500, Loic Prylli wrote:
> 
> Not knowing whether there is any chipset with the visibility feature,
> but without the retry capability, and given that CRS is irrelevant for
> most Linux platforms (it only matters just after power-on, long before
> Linux is started in the common case),

"common case" I suppose in your mouth means desktop machines ? :-)

In the embedded world, I would expect CRS to be something that linux has
to deal with regulary. Maybe enable_crs should be moved to quirks on
those platforms who want it...

> This is mostly independant, allowing a PCIE->PCI-X bridge to generate
> CRS is a different bit (bit 15 of pcie->devctl on the bridge). FWIW,
> Linux does not seem to touch it, and it defaults to zero, so it does
> not
> seem like most current PCIE->PCI-X bridge will never generates a CRS
> (some BIOSes might do it, but not the couple of platforms I looked
> at).
> Again the choice of setting here seems something better left to the
> specific BIOS/embedded-code for a given platform.

Ok, I wasn't sure about that one.

Ben.


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