pci: Don't enable aspm before drivers have had a chance to veto it
PATCH 1/1 pci: Don't enable aspm before drivers have had a chance to veto it
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after pci_enable_device() is called. This allows the driver to blacklist individual devices beforehand.
---
Cleaned up slightly to remove the hacky aspm_policy changing.
drivers/pci/pcie/aspm.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)
drivers/pci/pcie/aspm.c +14 -2
@@ -588,11 +588,23 @@ void pcie_aspm_init_link_state(struct pci_dev *pdev)* update through pcie_aspm_cap_init(). */ pcie_aspm_cap_init (link, blacklist); -pcie_config_aspm_path (link);/* Setup initial Clock PM state */ pcie_clkpm_cap_init (link, blacklist); -pcie_set_clkpm (link,policy_to_clkpm_state (link)); + +/* +* At this stage drivers haven't had an opportunity to change the +* link policy setting. Enabling ASPM on broken hardware can cripple +* it even before the driver has had a chance to disable ASPM, so +* default to a safe level right now. If we're enabling ASPM beyond +* the BIOS's expectation, we'll do so once pci_enable_device() is +* called. +*/ +if (aspm_policy !=POLICY_POWERSAVE ) { +pcie_config_aspm_path (link); +pcie_set_clkpm (link,policy_to_clkpm_state (link)); + } + unlock:mutex_unlock (&aspm_lock); out:
Signature · 1 line
1.7.0.1
Quoted 46 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett<[email protected]>---
Cleaned up slightly to remove the hacky
aspm_policychanging.drivers/pci/pcie/aspm.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)drivers/pci/pcie/aspm.c +14
-2@@ -588,11 +588,23 @@ void pcie_aspm_init_link_state(struct pci_dev *pdev)* update through pcie_aspm_cap_init(). */ pcie_aspm_cap_init (link, blacklist); -pcie_config_aspm_path (link);/* Setup initial Clock PM state */ pcie_clkpm_cap_init (link, blacklist); -pcie_set_clkpm (link,policy_to_clkpm_state (link)); + +/* +* At this stage drivers haven't had an opportunity to change the +* link policy setting. Enabling ASPM on broken hardware can cripple +* it even before the driver has had a chance to disable ASPM, so +* default to a safe level right now. If we're enabling ASPM beyond +* the BIOS's expectation, we'll do so once pci_enable_device() is +* called. +*/ +if (aspm_policy !=POLICY_POWERSAVE ) { +pcie_config_aspm_path (link); +pcie_set_clkpm (link,policy_to_clkpm_state (link)); + } + unlock:mutex_unlock (&aspm_lock); out:
Quoted 33 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Cleaned up slightly to remove the hacky
aspm_policychanging.drivers/pci/pcie/aspm.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)drivers/pci/pcie/aspm.c +4
-2@@ -588,11 +588,23 @@ void pcie_aspm_init_link_state(struct pci_dev *pdev)* update through pcie_aspm_cap_init(). */ pcie_aspm_cap_init (link, blacklist); -pcie_config_aspm_path (link);/* Setup initial Clock PM state */ pcie_clkpm_cap_init (link, blacklist); -pcie_set_clkpm (link,policy_to_clkpm_state (link)); + +/* +* At this stage drivers haven't had an opportunity to change the +* link policy setting. Enabling ASPM on broken hardware can cripple
drivers/pci/pcie/aspm.c void pcie_aspm_init_link_state(struct pci_dev *pdev) · line 607
Quoted 10 lines
drivers/pci/pcie/aspm.c +9
-0+* it even before the driver has had a chance to disable ASPM, so +* default to a safe level right now. If we're enabling ASPM beyond +* the BIOS's expectation, we'll do so once pci_enable_device() is +* called. +*/ +if (aspm_policy !=POLICY_POWERSAVE ) { +pcie_config_aspm_path (link); +pcie_set_clkpm (link,policy_to_clkpm_state (link)); + }
Matthew, isn't it so that the POLICY_DEFAULT will pass the above test and possibly switch the ASPM on?
tomas
Quoted 5 lines
drivers/pci/pcie/aspm.c +1
-0+ unlock:mutex_unlock (&aspm_lock);out:
Quoted 2 lines · Tomas Henzl
Matthew, isn't it so that the
POLICY_DEFAULTwill pass the above test and possibly switch the ASPM on?
Yes. We assume that the BIOS authors aren't actively malicious.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 8 lines · Matthew Garrett
Quoted 3 lines · Tomas Henzl
Matthew, isn't it so that the
POLICY_DEFAULTwill pass the above test and possibly switch the ASPM on?Yes. We assume that the BIOS authors aren't actively malicious.
I originally thought your patch is about not enabling ASPM on broken hardware (bios included) before the driver has a chance to change it.
Sorry for the confusion, I was wrong with the bios.
tomas
Quoted 11 lines · Tomas Henzl
Quoted 8 lines · Matthew Garrett
Quoted 3 lines · Tomas Henzl
Matthew, isn't it so that the
POLICY_DEFAULTwill pass the above test and possibly switch the ASPM on?Yes. We assume that the BIOS authors aren't actively malicious.
I originally thought your patch is about not enabling ASPM on broken hardware (bios included) before the driver has a chance to change it.
Heh. No, if the BIOS set up ASPM on the controller, it seems like it's safe to do the same. That's been the default behaviour of upstream for some time now.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.
Unfortenuly BIOS (news at 11) enables L0S.
Its easy to disable ASPM from driver. It just a matter of calling pci_disable_link_state.
However, that depends on CONFIG_PCIEASPM.
How about making pci_disable_link_state always available or even better, just make CONFIG_PCIEASPM unconditional?
Btw, this is my last linux problem that had slim chances to be solved. The other one was s2ram hang on my primary notebook.
This just shows that in linux everyone helps each other.
I fixed almost impossible s2ram problem on my notebook. Jussi Kivilinna fixed almost impossible to solve problem on my aspire one.
Best regards,
Maxim Levitsky
Quoted 21 lines · On Fri, 18 Jun 2010 15:06:51 +0300 Maxim Levitsky <[email protected]>…
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.Unfortenuly BIOS (news at 11) enables L0S.
Quoted 7 lines
Its easy to disable ASPM from driver. It just a matter of calling
pci_disable_link_state.However, that depends on
CONFIG_PCIEASPM.How about making
pci_disable_link_statealways available or even better, just makeCONFIG_PCIEASPMunconditional?
The former is ok with me. Care to post a patch?
Thanks,
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Quoted 27 lines · Jesse Barnes
Quoted 24 lines · On Fri, 18 Jun 2010 15:06:51 +0300 Maxim Levitsky <[email protected]>…
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.Unfortenuly BIOS (news at 11) enables L0S.
Its easy to disable ASPM from driver. It just a matter of calling
pci_disable_link_state.
Quoted 6 lines
Quoted 4 lines
However, that depends on
CONFIG_PCIEASPM.How about making
pci_disable_link_statealways available or even better, just makeCONFIG_PCIEASPMunconditional?The former is ok with me. Care to post a patch?
It not that simple at first glance.
This functions uses plenty of code from the aspm.c, therefore care should be taken to do that properly.
Of course the easy solution is to compile all code in always, and just disable it by runtime switch (it even exists, aspm_disabled) Or, another easy solution is to make ath5k depend on CONFIG_PCIEASPM
What do you think?
Best regards,
Maxim Levitsky
Quoted 38 lines · On Fri, 18 Jun 2010 20:05:42 +0300 Maxim Levitsky <[email protected]>…
Quoted 27 lines · Jesse Barnes
Quoted 24 lines · On Fri, 18 Jun 2010 15:06:51 +0300 Maxim Levitsky <[email protected]>…
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.Unfortenuly BIOS (news at 11) enables L0S.
Its easy to disable ASPM from driver. It just a matter of calling
pci_disable_link_state.Quoted 6 lines
Quoted 4 lines
However, that depends on
CONFIG_PCIEASPM.How about making
pci_disable_link_statealways available or even better, just makeCONFIG_PCIEASPMunconditional?The former is ok with me. Care to post a patch?
It not that simple at first glance.
This functions uses plenty of code from theaspm.c, therefore care should be taken to do that properly.
Quoted 5 lines
Of course the easy solution is to compile all code in always, and just disable it by runtime switch (it even exists,
aspm_disabled) Or, another easy solution is to make ath5k depend onCONFIG_PCIEASPMWhat do you think?
I do like the idea of getting rid of config options. I just want to make sure we don't regress people, so I need to double check the default behavior, especially for non-x86 and see whether it'll generally be a no-op or not.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Quoted 38 lines · On Fri, 18 Jun 2010 20:05:42 +0300 Maxim Levitsky <[email protected]>…
Quoted 27 lines · Jesse Barnes
Quoted 24 lines · On Fri, 18 Jun 2010 15:06:51 +0300 Maxim Levitsky <[email protected]>…
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.Unfortenuly BIOS (news at 11) enables L0S.
Its easy to disable ASPM from driver. It just a matter of calling
pci_disable_link_state.Quoted 6 lines
Quoted 4 lines
However, that depends on
CONFIG_PCIEASPM.How about making
pci_disable_link_statealways available or even better, just makeCONFIG_PCIEASPMunconditional?The former is ok with me. Care to post a patch?
It not that simple at first glance.
This functions uses plenty of code from theaspm.c, therefore care should be taken to do that properly.
Quoted 5 lines
Of course the easy solution is to compile all code in always, and just disable it by runtime switch (it even exists,
aspm_disabled) Or, another easy solution is to make ath5k depend onCONFIG_PCIEASPMWhat do you think?
So unless a device is *really* broken, it seems like the default policy should be ok across the board. So let's get a CONFIG_PCIEASPM removal patch into the 2.6.36 merge window early to flush out any potential problems.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Quoted 45 lines · Jesse Barnes
Quoted 42 lines · On Fri, 18 Jun 2010 20:05:42 +0300 Maxim Levitsky <[email protected]>…
Quoted 27 lines · Jesse Barnes
Quoted 24 lines · On Fri, 18 Jun 2010 15:06:51 +0300 Maxim Levitsky <[email protected]>…
Quoted 10 lines · Matthew Garrett
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Hi,
I recently discovered that my aspire one wireless troubles (card just dies after a while) are caused by ASPM L0S state.
The device (AR5001) seems to have a hardware bug, and it also disables L0S in windows driver.Unfortenuly BIOS (news at 11) enables L0S.
Its easy to disable ASPM from driver. It just a matter of calling
pci_disable_link_state.Quoted 6 lines
Quoted 4 lines
However, that depends on
CONFIG_PCIEASPM.How about making
pci_disable_link_statealways available or even better, just makeCONFIG_PCIEASPMunconditional?The former is ok with me. Care to post a patch?
It not that simple at first glance.
This functions uses plenty of code from theaspm.c, therefore care should be taken to do that properly.Of course the easy solution is to compile all code in always, and just disable it by runtime switch (it even exists,
aspm_disabled) Or, another easy solution is to make ath5k depend onCONFIG_PCIEASPM
Quoted 6 lines
Quoted 1 line
What do you think?
So unless a device is *really* broken, it seems like the default policy should be ok across the board. So let's get a
CONFIG_PCIEASPMremoval patch into the 2.6.36 merge window early to flush out any potential problems.
It would be perfect for me.
Best regards,
Maxim Levitsky
Jesse Barnes
AppliedQuoted 36 lines · On Wed, 9 Jun 2010 16:05:07 -0400 Matthew Garrett <[email protected]> wrote:
The aspm code will currently set the configured aspm policy before drivers have had an opportunity to indicate that their hardware doesn't support it. Unfortunately, putting some hardware in L0 or L1 can result in the hardware no longer responding to any requests, even after aspm is disabled. It makes more sense to leave aspm policy at the BIOS defaults at initial setup time, reconfiguring it after
pci_enable_device()is called. This allows the driver to blacklist individual devices beforehand.Signed-off-by Matthew Garrett <[email protected]>---
Cleaned up slightly to remove the hacky
aspm_policychanging.drivers/pci/pcie/aspm.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)drivers/pci/pcie/aspm.c +7
-2@@ -588,11 +588,23 @@ void pcie_aspm_init_link_state(struct pci_dev *pdev)* update through pcie_aspm_cap_init(). */ pcie_aspm_cap_init (link, blacklist); -pcie_config_aspm_path (link);/* Setup initial Clock PM state */ pcie_clkpm_cap_init (link, blacklist); -pcie_set_clkpm (link,policy_to_clkpm_state (link)); + +/* +* At this stage drivers haven't had an opportunity to change the +* link policy setting. Enabling ASPM on broken hardware can cripple +* it even before the driver has had a chance to disable ASPM, so +* default to a safe level right now. If we're enabling ASPM beyond +* the BIOS's expectation, we'll do so once pci_enable_device() is
drivers/pci/pcie/aspm.c void pcie_aspm_init_link_state(struct pci_dev *pdev) · line 610
Quoted 10 lines
drivers/pci/pcie/aspm.c +7
-0+* called. +*/ +if (aspm_policy !=POLICY_POWERSAVE ) { +pcie_config_aspm_path (link); +pcie_set_clkpm (link,policy_to_clkpm_state (link)); + } + unlock:mutex_unlock (&aspm_lock); out:
Applied to linux-next, thanks.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center