Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in

Jesse Barnes
2008-01-31T05:59:19Z

On Tuesday 29 January 2008 05:19:55 am Greg KH wrote:
> Hahahaha, oh, that's a good one...
>
> But what about the thousands of implementations out there that are
> buggy?
>
> I'm with Arjan here, I'm very skeptical.

Ugg, let's look at the actual data (again); I'm really not sure why people
are jumping to such dire conclusions about the current state of things.

AIUI we only have 3 issues so far (remember mmconfig has been enabled in -mm
for a long time):
1) host bridge decode problems (disabling decode to avoid overlaps can
cause some bridges to stop decoding RAM addrs, but we have a fix for that)
2) config space retry on ATI (I think willy already debunked this one?)
3) some FUD about SMM or other firmware interrupts coming in during BAR
sizing while decode is disabled (this one is just pure FUD; if we want to
solve it properly we need a new platform hook to disable SMM/NMI/etc.
around PCI probing)

What else was there? What reason do we have to think that things are so
disastrous?

So I really prefer willy's approach to Arjan's alternative...

Jesse