From: Bjorn Helgaas <helgaas@kernel.org>
To: Ocean HY1 He <hehy1@lenovo.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"wangyijing@huawei.com" <wangyijing@huawei.com>,
"luto@kernel.org" <luto@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"prarit@redhat.com" <prarit@redhat.com>,
"jcm@redhat.com" <jcm@redhat.com>,
Nagananda Chumbalkar <nchumbalkar@lenovo.com>
Subject: Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream
Date: Tue, 24 May 2016 06:53:33 -0500 [thread overview]
Message-ID: <20160524115333.GA19140@localhost> (raw)
In-Reply-To: <1464071269-79954-1-git-send-email-hehy1@lenovo.com>
Hi Ocean,
On Tue, May 24, 2016 at 06:29:44AM +0000, Ocean HY1 He wrote:
> In pcie_config_aspm_link(), when convert ASPM state to
> upstream/downstream ASPM register state, the upstream variable and
> dwsream variable are reversed. This causes PCI/E link enter ASPM L0s
> even it should be disabled and PCI/E endpoint may reset randomly.
Random resets of an endpoint sounds like a pretty bad problem. Do you
have a bug report? We've had lots of issues with ASPM; I wonder if
this could account for some of them.
> Signed-off-by: Ocean He <hehy1@lenovo.com>
> ---
> drivers/pci/pcie/aspm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index 2dfe7fd..3f8a44d 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -439,9 +439,9 @@ static void pcie_config_aspm_link(struct pcie_link_state *link, u32 state)
> return;
> /* Convert ASPM state to upstream/downstream ASPM register state */
> if (state & ASPM_STATE_L0S_UP)
> - dwstream |= PCI_EXP_LNKCTL_ASPM_L0S;
> - if (state & ASPM_STATE_L0S_DW)
> upstream |= PCI_EXP_LNKCTL_ASPM_L0S;
> + if (state & ASPM_STATE_L0S_DW)
> + dwstream |= PCI_EXP_LNKCTL_ASPM_L0S;
> if (state & ASPM_STATE_L1) {
> upstream |= PCI_EXP_LNKCTL_ASPM_L1;
> dwstream |= PCI_EXP_LNKCTL_ASPM_L1;
> --
> 1.8.3.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-24 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:29 [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Ocean HY1 He
2016-05-24 11:53 ` Bjorn Helgaas [this message]
2016-05-24 14:42 ` Sinan Kaya
2016-05-25 16:36 ` Bjorn Helgaas
2016-05-25 12:58 ` Ocean HY1 He
2016-05-25 16:57 ` Bjorn Helgaas
2016-05-25 17:21 ` Sinan Kaya
2016-05-25 17:50 ` Bjorn Helgaas
2016-05-25 18:19 ` Sinan Kaya
2016-05-25 18:33 ` Bjorn Helgaas
2016-05-25 20:44 ` Sinan Kaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160524115333.GA19140@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=hehy1@lenovo.com \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nchumbalkar@lenovo.com \
--cc=prarit@redhat.com \
--cc=wangyijing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox