On Tue, Jun 22, 2010 at 10:25 AM, Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > On Tue, Jun 22, 2010 at 10:17:11AM -0700, Luis R. Rodriguez wrote: >> On Tue, Jun 22, 2010 at 9:52 AM, Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: >> > Why would you only want to enable ASPM for one device? >> >> ASPM doesn't always work for all devices even if they do advertise >> ASPM capability so turning it on selectively by device is what I >> recommend since otherwise you may get hangs and you will then have to >> do the selective enabling. > > Right, which we have to deal with by having drivers disable ASPM on > broken devices. Agreed, but then the assumption would be drivers are ASPM bug free which is expect to be false with Video and 802.11 given that only a handful of vendors do actually get involved with their drivers upstream. Safe thing of course is to just disable it, of course, but if you are going to use pcie_aspm=force good luck! >> Furthermore laptops tend to disable ASPM for cards not built-in to it, >> an example is Cardbus slots or internal PCI-E slots. This is often >> done because to enable ASPM for some cards you often need to tune the >> host controller in addition to enabling ASPM for the endpoint, so this >> will vary depending on vendor, chipset, and host controller >> combination. This is documentation that the OEM / ODM typically end up >> getting, but not end users. > > Having looked into this, Windows will enable ASPM on external > controllers unless there's some reason for it not to - where that may be > either the appropriate bit in the FADT being set, the device not being > PCIe 1.1 or later, there being no _OSC method on the appropriate root > bridge or the _OSC method not giving it full control over PCIe, the > driver disabling ASPM or the device not advertising it in the first > place. I was unaware of all this root complex sanity checks on Windows, thanks for sharing. > Are you aware of any other cases where Windows will refuse to > enable ASPM? My point was not whether or not ASPM typically got enabled on Windows Vs Linux, my point was more of the fact that for some endpoint devices you may have to tweak the root complex to get ASPM properly working and that these tweaks *are* implemented on the BIOS by the ODM / OEM for those devices and that the documentation for such tweaks is not typically public. So, if you are like me and cannot stand the internal 802.11 card on your laptop and want to replace it with something else you are stuck to hoping such BIOS tweaks are either not required or figuring out what the tweaks are yourself and doing them through userspace for the root complex *prior* to enabling ASPM through userspace as well for the endpoint. I suspect these tweaks will go away as the industry produces cards with both L1 and L0s enabled all the time (devices being produced today), but for devices caught in that middle of time between whether or not L0s would be *required* (last 2 years) I suspect we'll run into these issues. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
