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

Brice Goglin wrote:er.

What would you think of a patch implementing the following strategy:
1) if MMCONFIG works, always use it (no change)
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)
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.

an OS isn't allowed to mix old and new access methods realistically so I don't think
this is a viable good solution...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
    • From: Brice Goglin <[email protected]>
  • Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
    • From: Andi Kleen <[email protected]>

• References:
  • [RFC] PCI extended conf space when MMCONFIG disabled because of e820
    • From: Brice Goglin <[email protected]>

• Prev by Date: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
• Next by Date: Re: [RFC] the /proc/filecache interface
• Previous by thread: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
• Next by thread: Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]