linux-kernel - Re: [PATCH]PCI:disable resource decode in PCI BAR detection

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070917133106.B21399@jurassic.park.msu.ru>
Date:	Mon, 17 Sep 2007 13:31:06 +0400
From:	Ivan Kokshaysky <ink@...assic.park.msu.ru>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Robert Hancock <hancockr@...w.ca>, Greg KH <gregkh@...e.de>,
	Shaohua Li <shaohua.li@...el.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-pci <linux-pci@...ey.karlin.mff.cuni.cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection

On Sun, Sep 16, 2007 at 01:52:59PM -0600, Matthew Wilcox wrote:
> I don't think it would be that complicated.  We could just delay probing
> for mmconfig until after the pci bus probes are done.  No changes to
> other architectures needed.

Indeed. Seems like it's a way to go.

> I'm really disappointed with mmconfig.  Here was a great chance to get
> rid of all the sucky performance problems of the past, and BIOS writers
> and chipset designers have fucked up the implementation so much that
> it's now the ugliest method for getting to pci config space.  And it's
> the *only* method of getting to extended config space.

Same feeling...

Fortunately, it seems that we don't access the extended config space
during bus probe.

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