mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: rdh@east.sun.com
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci/pcie: Avoid unnecessary PCIe link retrains
Date: Wed, 4 Nov 2009 11:03:21 -0800	[thread overview]
Message-ID: <20091104110321.5e58e112@jbarnes-piketon> (raw)
In-Reply-To: <19184.41676.262206.134000@gargle.gargle.HOWL>

[Cc'ing linux-pci@vger.kernel.org too]

On Tue, 3 Nov 2009 16:38:20 -0500
RDH <rdh@east.sun.com> wrote:

> 
> This patch avoids unnecessary PCIe link retraining sequences within
> the PCIe ASPM common clock setup code by issuing a link retrain
> command only if we are actually changing the PCIe clock configuration.
> 
> Signed-off-by: Robert D. Houk <rdh@East.Sun.COM>
> ---
>  aspm.c |   20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> --- a/drivers/pci/pcie/aspm.c	2009-10-15 20:41:50.000000000
> -0400 +++ b/drivers/pci/pcie/aspm.c	2009-11-02
> 14:29:35.000000000 -0500 @@ -183,6 +183,7 @@ static void
> pcie_aspm_configure_common_c {
>  	int ppos, cpos, same_clock = 1;
>  	u16 reg16, parent_reg, child_reg[8];
> +	u16 lnkctl_ccc_or, lnkctl_ccc_and;
>  	unsigned long start_jiffies;
>  	struct pci_dev *child, *parent = link->pdev;
>  	struct pci_bus *linkbus = parent->subordinate;
> @@ -205,6 +206,25 @@ static void pcie_aspm_configure_common_c
>  	if (!(reg16 & PCI_EXP_LNKSTA_SLC))
>  		same_clock = 0;
>  
> +	/* Check upstream component for Common Clock Config */
> +	pci_read_config_word(parent, ppos + PCI_EXP_LNKCTL, &reg16);
> +	lnkctl_ccc_and = lnkctl_ccc_or = (reg16 &
> PCI_EXP_LNKCTL_CCC); +
> +	/* Scan downstream component for CCC, all functions */
> +	list_for_each_entry(child, &linkbus->devices, bus_list) {
> +		cpos = pci_find_capability(child, PCI_CAP_ID_EXP);
> +		pci_read_config_word(child, cpos + PCI_EXP_LNKCTL,
> &reg16);
> +		lnkctl_ccc_and &= (reg16 & PCI_EXP_LNKCTL_CCC);
> +		lnkctl_ccc_or |= (reg16 & PCI_EXP_LNKCTL_CCC);
> +	}
> +
> +	/* If we want Common Clock OFF and no device/function has it
> on */
> +	/* or we want Common Clock ON and every device/function has
> it on */
> +	/* then there is no need to retrain PCIe links */
> +	if (((same_clock == 0) && (lnkctl_ccc_or == 0))
> +            || ((same_clock == 1) && (lnkctl_ccc_and ==
> PCI_EXP_LNKCTL_CCC)))
> +		return;		/* Don't retrain link(s) */
> +
>  	/* Configure downstream component, all functions */
>  	list_for_each_entry(child, &linkbus->devices, bus_list) {
>  		cpos = pci_find_capability(child, PCI_CAP_ID_EXP);
> 

Seems ok to me, anyone have comments?

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-11-04 19:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 21:38 RDH
2009-11-04 19:03 ` Jesse Barnes [this message]
2009-11-04 23:28   ` Bjorn Helgaas
2009-11-05  3:05     ` Kenji Kaneshige
2009-11-05 18:59       ` Bjorn Helgaas
2009-11-05 19:07         ` Matthew Wilcox
2009-11-05 20:29           ` Bjorn Helgaas
2009-11-06  1:15             ` Kenji Kaneshige
2009-11-05 19:11       ` Matthew Wilcox
2009-11-06  2:48         ` Kenji Kaneshige
2009-11-06 22:00       ` Jesse Barnes
2009-11-05  1:38   ` Kenji Kaneshige

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=20091104110321.5e58e112@jbarnes-piketon \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdh@east.sun.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

all inboxes | Powered by JetHome®