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]
Date:	Tue, 30 Oct 2007 10:43:57 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Robert Hancock <hancockr@...w.ca>, Greg KH <greg@...ah.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	akpm@...ux-foundation.org, ak@...e.de, rajesh.shah@...el.com,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch



On Tue, 30 Oct 2007, Arjan van de Ven wrote:
> 
> something like
> int pci_enable_mmconfig(struct pci_dev *pdev) ?

Yes, that looks fine. It also matches the kinds of things drivers already 
have to do (ie enable DMA, MSI etc), both conceptually and from a purely 
syntactic/practical standpoint.

I think mmconfig and MSI have a lot in common, in that both are relatively 
new features and both have had issues that made them not work well.

> sounds like a very solid plan to me...
> 
> > Maybe somebody inside Intel could just clarify the documentation, and 
> > change it from "you're not supposed to mix" to "mix all you want". 
> 
> I'll see what I can do ;)

Well, let's see if "pci_enable_mmconfig()" works out first. There probably 
aren't more than a few drivers that would be interested in this anyway, so 
it's probably fine.

And by the time mmconfig is commonly used, probably all the teething 
problems are long gone, so we could plan on a "in five years, maybe we 
could even enable it by default" thing?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ