From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Robert Hancock <hancockr@shaw.ca>, Greg KH <greg@kroah.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
akpm@linux-foundation.org, ak@suse.de, rajesh.shah@intel.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch
Date: Tue, 30 Oct 2007 10:43:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710301039230.30120@woody.linux-foundation.org> (raw)
In-Reply-To: <20071030102820.47a6e365@laptopd505.fenrus.org>
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
next prev parent reply other threads:[~2007-10-30 17:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708151919.l7FJJfUE010966@imap1.linux-foundation.org>
2007-10-25 23:20 ` - mmconfig-validate-against-acpi-motherboard-resources.patch removed from -mm tree Robert Hancock
2007-10-25 23:22 ` Jesse Barnes
2007-10-26 2:54 ` Greg KH
2007-10-26 5:03 ` Robert Hancock
2007-10-26 5:27 ` Greg KH
2007-10-26 16:58 ` Jesse Barnes
2007-10-26 16:59 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Jesse Barnes
2007-10-27 2:41 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Greg KH
2007-10-29 23:52 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Robert Hancock
2007-10-30 15:15 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 16:47 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Arjan van de Ven
2007-10-30 17:07 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 17:28 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Arjan van de Ven
2007-10-30 17:43 ` Linus Torvalds [this message]
2007-11-01 8:31 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Martin Mares
2007-11-01 14:08 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Arjan van de Ven
2007-11-08 13:50 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Martin Mares
2007-10-30 22:04 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Jesse Barnes
2007-10-30 22:22 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 22:31 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Jesse Barnes
2007-10-30 22:44 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch David Miller
2007-10-30 22:48 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 22:38 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 22:39 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Jesse Barnes
2007-10-30 23:30 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Andi Kleen
2007-10-30 23:41 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Robert Hancock
2007-10-30 23:52 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Arjan van de Ven
2007-10-31 0:02 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 23:59 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-31 0:23 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Robert Hancock
2007-10-31 1:30 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Jesse Barnes
2007-10-30 18:50 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Andi Kleen
2007-10-30 19:06 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
2007-10-30 19:37 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Andi Kleen
2007-10-30 21:41 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.999.0710301039230.30120@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=hancockr@shaw.ca \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajesh.shah@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®