Linus Torvalds wrote:
(For example: I have three machines that I know have working MMCONF. On only one of theose does Linux actually even enable MMCONF accesses, because on the two other ones the BIOSes do the crazy "put it in some space that is reserved by PnP crap later", so we actually refuse to touch it. So at least in my limited environment, we hardly get any MMCONFIG test coverage, exactly because we have to be so totally anal about not enabling it early, because we cannot guarantee that it's not clashing with anything else).
Definitely. So, two questions:What's the preferred way to deal with the desire to view extended config space with "lspci -vvvxxx"?
Right now, we enable mmconfig for the bus/domain range requested by the BIOS [heh, so by implication many early BIOSen stomp themselves].
Is there a path for hw vendors, after passing 1,001 anal checks, to maintain the current behavior as it exists today in arch/x86/pci/mmconfig_{32,64}.c?
Jeff -- 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:
- References:
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Arjan van de Ven <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Linus Torvalds <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Linus Torvalds <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Linus Torvalds <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Loic Prylli <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Ivan Kokshaysky <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Linus Torvalds <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Prev by Date: Re: [RFC/PATCH 4/4] [POWERPC] pci: Disable IO/Mem on a device when resources can't be allocated
- Next by Date: relation between mmc_request, mmc_data and mmc_command
- Previous by thread: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Next by thread: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Index(es):
 |