[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.999.0710300811230.30120@woody.linux-foundation.org>
Date: Tue, 30 Oct 2007 08:15:46 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Robert Hancock <hancockr@...w.ca>
cc: 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 Mon, 29 Oct 2007, Robert Hancock wrote:
>
> The other possible workaround would be to avoid using MMCONFIG until the BAR
> sizing is done.
The only sane solution is the one that people constantly seem to ignore:
- only use MMCONFIG if absolutely required by the access itself
In other words, make the MMCONFIG code fall back on old-style accesses for
any register access to a word with reg+size <= 256.
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?
The fact is, CONF1 style accesses are just safer, and *work*.
Can we please just do that?
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