Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820

[Andi Kleen <ak@suse.de>]

Arjan van de Ven <arjan@linux.intel.com> writes:

> Brice Goglin wrote:er.
> > What would you think of a patch implementing the following strategy:
> > 1) if MMCONFIG works, always use it (no change)

One problem in your proposal Bryan is that just trying to access
bogus hardware mappings might cause nasty effects like machine
checks or trigger chipset errata.

> > 2) if MMCONFIG is disabled and we are accessing the regular config
> > space, use direct conf (no change, should ensure that any machine will
> > still boot fine)

That's already the case.

> > 3) if MMCONFIG is disabled but we are accessing the _extended_ config
> > space, try mmconfig anyway since there's no other way to do it.

(3) sounds dangerous to me.

> an OS isn't allowed to mix old and new access methods realistically so I don't think
> this is a viable good solution...

Why is it not allowed? We already do it in some cases.

Anyways I would say that if the BIOS can't get MCFG right then 
it's likely not been validated on that board and shouldn't be used.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/