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

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: <20071222080249.482fab0b@laptopd505.fenrus.org>
Date:	Sat, 22 Dec 2007 08:02:49 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	gregkh@...e.de, linux-pci@...ey.karlin.mff.cuni.cz,
	torvalds@...ux-foundation.org
Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a
 driver opt-in issue

On Sat, 22 Dec 2007 08:54:37 -0700
Matthew Wilcox <matthew@....cx> wrote:

> On Sat, Dec 22, 2007 at 06:47:19AM -0800, Arjan van de Ven wrote:
> > Do you hate the name or the concept? I'm certainly open for a
> > better name.... 
> 
> I hate the concept.  We should just fall back to type1 accesses on
> mmconfig machines for all accesses below 64 bytes, as Ivan suggested.

I assume you meant 256 not 64;

even then.. it's technically not correct; you're not supposed to mix access types for the same device..
Just doing opt-in also allows us to do quirks (forbid access) as well.


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/