From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Robert Hancock <hancockr@shaw.ca>, Greg KH <greg@kroah.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
akpm@linux-foundation.org, 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 19:50:58 +0100 [thread overview]
Message-ID: <200710301950.58519.ak@suse.de> (raw)
In-Reply-To: <alpine.LFD.0.999.0710300811230.30120@woody.linux-foundation.org>
> At that point, almost all the issues with mmconfig just go away, BECAUSE
> NOBODY USES IT, so it doesn't matter if it's broken?
We seem to slowly grow more uses of registers > 256, but yes it's still mostly
non critical stuff.
> The fact is, CONF1 style accesses are just safer, and *work*.
>
> Can we please just do that?
At least for the AMD GART IOMMU I would prefer if that was not done.
It has a pci config space access in a time critical path (flush).
And Family10h supports accessing the northbridge using mmconfig.
I believe the tigon3 driver also does config space access frequently
on some chips.
Also there are still the old x86 Macs where conf1 doesn't work.
-Andi
next prev parent reply other threads:[~2007-10-30 18:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 19:19 - mmconfig-validate-against-acpi-motherboard-resources.patch removed from -mm tree akpm
2007-10-25 23:20 ` 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 ` pci-disable-decode-of-io-memory-during-bar-sizing.patch Linus Torvalds
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 ` Andi Kleen [this message]
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=200710301950.58519.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hancockr@shaw.ca \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajesh.shah@intel.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.