From: Pavel Machek <pavel@suse.cz>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
matthew@wil.cx, shaohua.li@intel.com
Subject: Re: [PATCH] ASPM: Use msleep instead of cpu_relax during link retraining
Date: Thu, 25 Dec 2008 20:01:29 +0100 [thread overview]
Message-ID: <20081225190129.GA1615@ucw.cz> (raw)
In-Reply-To: <20081222221156.29645.95982.stgit@bluto>
On Mon 2008-12-22 15:11:57, Andrew Patterson wrote:
> ASPM: Use msleep instead of cpu_relax during link retraining
>
> The cpu_relax() function can be a noop on certain architectures
> like IA-64 when CPU threads are disabled, so use msleep instead
> during link retraining busy/wait loop.
Author clearly wanted to do a busy loop... why do you think 10msec
delay here is acceptable?
> Introduce define LINK_RETRAIN_TIMEOUT instead of hard-coding
> timeout in pcie_aspm_configure_common_clock.
>
> Signed-off-by: Andrew Patterson <andrew.patterson@hp.com>
> @@ -70,6 +71,8 @@ static const char *policy_str[] = {
> [POLICY_POWERSAVE] = "powersave"
> };
>
> +#define LINK_RETRAIN_TIMEOUT HZ
> +
> static int policy_to_aspm_state(struct pci_dev *pdev)
> {
> struct pcie_link_state *link_state = pdev->link_state;
> @@ -217,16 +220,18 @@ static void pcie_aspm_configure_common_clock(struct pci_dev *pdev)
> pci_write_config_word(pdev, pos + PCI_EXP_LNKCTL, reg16);
>
> /* Wait for link training end */
> - /* break out after waiting for 1 second */
> + /* break out after waiting for timeout */
> start_jiffies = jiffies;
> - while ((jiffies - start_jiffies) < HZ) {
> + for (;;) {
> pci_read_config_word(pdev, pos + PCI_EXP_LNKSTA, ®16);
> if (!(reg16 & PCI_EXP_LNKSTA_LT))
> break;
> - cpu_relax();
> + if ((jiffies - start_jiffies) >= LINK_RETRAIN_TIMEOUT)
> + break;
> + msleep(1);
Is this safe w.r.t. jiffie wraparounds?
> }
> /* training failed -> recover */
> - if ((jiffies - start_jiffies) >= HZ) {
> + if ((jiffies - start_jiffies) >= LINK_RETRAIN_TIMEOUT) {
> dev_printk (KERN_ERR, &pdev->dev, "ASPM: Could not configure"
> " common clock\n");
> i = 0;
AFAICT this can trigger false positives. !reg16 test succeeds and then
jiffies tick.
...it could happen before but you make it way more probable...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-12-25 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 22:11 [PATCH] ASPM: Use msleep instead of cpu_relax during link retraining Andrew Patterson
2008-12-25 19:01 ` Pavel Machek [this message]
2008-12-25 23:24 ` Matthew Wilcox
2008-12-26 18:27 ` Pavel Machek
2009-01-05 19:17 ` Jesse Barnes
2009-01-05 19:40 ` Andrew Patterson
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=20081225190129.GA1615@ucw.cz \
--to=pavel@suse.cz \
--cc=andrew.patterson@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=shaohua.li@intel.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