From: Bjorn Helgaas <helgaas@kernel.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: hkallweit1@gmail.com, nic_swsd@realtek.com, bhelgaas@google.com,
koba.ko@canonical.com, acelan.kao@canonical.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sathyanarayanan.kuppuswamy@linux.intel.com,
vidyas@nvidia.com, rafael.j.wysocki@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH net-next v9 3/5] r8169: Consider chip-specific ASPM can be enabled on more cases
Date: Thu, 9 Mar 2023 14:17:05 -0600 [thread overview]
Message-ID: <20230309201705.GA1165139@bhelgaas> (raw)
In-Reply-To: <20230225034635.2220386-4-kai.heng.feng@canonical.com>
On Sat, Feb 25, 2023 at 11:46:33AM +0800, Kai-Heng Feng wrote:
> To really enable ASPM on r8169 NICs, both standard PCIe ASPM and
> chip-specific ASPM have to be enabled at the same time.
>
> Before enabling ASPM at chip side, make sure the following conditions
> are met:
> 1) Use pcie_aspm_support_enabled() to check if ASPM is disabled by
> kernel parameter.
> 2) Use pcie_aspm_capable() to see if the device is capable to perform
> PCIe ASPM.
> 3) Check the return value of pci_disable_link_state(). If it's -EPERM,
> it means BIOS doesn't grant ASPM control to OS, and device should use
> the ASPM setting as is.
>
> Consider ASPM is manageable when those conditions are met.
>
> While at it, disable ASPM at chip-side for TX timeout reset, since
> pci_disable_link_state() doesn't have any effect when OS isn't granted
> with ASPM control.
1) "While at it, ..." is always a hint that maybe this part could be
split to a separate patch.
2) The mix of chip-specific and standard PCIe ASPM configuration is a
mess. Does it *have* to be intermixed at run-time, or could all the
chip-specific stuff be done once, e.g., maybe chip-specific ASPM
enable could be done at probe-time, and then all subsequent ASPM
configuration could done via the standard PCIe registers?
I.e., does the chip work correctly if chip-specific ASPM is enabled,
but standard PCIe ASPM config is *disabled*?
The ASPM sysfs controls [1] assume that L0s, L1, L1.1, L1.2 can all be
controlled simply by using the standard PCIe registers. If that's not
the case for r8169, things will break when people use the sysfs knobs.
Bjorn
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-bus-pci?id=v6.2#n420
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
> v9:
> - No change.
>
> v8:
> - Enable chip-side ASPM only when PCIe ASPM is already available.
> - Wording.
>
> v7:
> - No change.
>
> v6:
> - Unconditionally enable chip-specific ASPM.
>
> v5:
> - New patch.
>
> drivers/net/ethernet/realtek/r8169_main.c | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/r8169_main.c b/drivers/net/ethernet/realtek/r8169_main.c
> index 45147a1016bec..a857650c2e82b 100644
> --- a/drivers/net/ethernet/realtek/r8169_main.c
> +++ b/drivers/net/ethernet/realtek/r8169_main.c
> @@ -2675,8 +2675,11 @@ static void rtl_disable_exit_l1(struct rtl8169_private *tp)
>
> static void rtl_hw_aspm_clkreq_enable(struct rtl8169_private *tp, bool enable)
> {
> - /* Don't enable ASPM in the chip if OS can't control ASPM */
> - if (enable && tp->aspm_manageable) {
> + /* Skip if PCIe ASPM isn't possible */
> + if (!tp->aspm_manageable)
> + return;
> +
> + if (enable) {
> RTL_W8(tp, Config5, RTL_R8(tp, Config5) | ASPM_en);
> RTL_W8(tp, Config2, RTL_R8(tp, Config2) | ClkReqEn);
>
> @@ -4545,8 +4548,13 @@ static void rtl_task(struct work_struct *work)
> /* ASPM compatibility issues are a typical reason for tx timeouts */
> ret = pci_disable_link_state(tp->pci_dev, PCIE_LINK_STATE_L1 |
> PCIE_LINK_STATE_L0S);
> +
> + /* OS may not be granted to control PCIe ASPM, prevent the driver from using it */
> + tp->aspm_manageable = 0;
> +
> if (!ret)
> netdev_warn_once(tp->dev, "ASPM disabled on Tx timeout\n");
> +
> goto reset;
> }
>
> @@ -5227,13 +5235,19 @@ static int rtl_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
> * Chips from RTL8168h partially have issues with L1.2, but seem
> * to work fine with L1 and L1.1.
> */
> - if (rtl_aspm_is_safe(tp))
> + if (!pcie_aspm_support_enabled() || !pcie_aspm_capable(pdev))
> + rc = -EINVAL;
> + else if (rtl_aspm_is_safe(tp))
> rc = 0;
> else if (tp->mac_version >= RTL_GIGA_MAC_VER_46)
> rc = pci_disable_link_state(pdev, PCIE_LINK_STATE_L1_2);
> else
> rc = pci_disable_link_state(pdev, PCIE_LINK_STATE_L1);
> - tp->aspm_manageable = !rc;
> +
> + /* -EPERM means BIOS doesn't grant OS ASPM control, ASPM should be use
> + * as is. Honor it.
> + */
> + tp->aspm_manageable = (rc == -EPERM) ? 1 : !rc;
>
> tp->dash_type = rtl_check_dash(tp);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-03-09 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 3:46 [PATCH net-next v9 0/5] r8169: Temporarily disable ASPM on NAPI poll Kai-Heng Feng
2023-02-25 3:46 ` [PATCH net-next v9 1/5] Revert "PCI/ASPM: Unexport pcie_aspm_support_enabled()" Kai-Heng Feng
2023-02-25 6:09 ` Sathyanarayanan Kuppuswamy
2023-02-25 3:46 ` [PATCH net-next v9 2/5] PCI/ASPM: Add pcie_aspm_capable() helper Kai-Heng Feng
2023-02-25 6:10 ` Sathyanarayanan Kuppuswamy
2023-02-25 3:46 ` [PATCH net-next v9 3/5] r8169: Consider chip-specific ASPM can be enabled on more cases Kai-Heng Feng
2023-02-25 6:13 ` Sathyanarayanan Kuppuswamy
2023-03-09 20:17 ` Bjorn Helgaas [this message]
2023-03-10 20:42 ` Heiner Kallweit
2023-03-10 20:48 ` Bjorn Helgaas
2023-02-25 3:46 ` [PATCH net-next v9 4/5] r8169: Use spinlock to guard config register locking Kai-Heng Feng
2023-02-25 6:16 ` Sathyanarayanan Kuppuswamy
2023-02-25 3:46 ` [PATCH net-next v9 5/5] r8169: Disable ASPM while doing NAPI poll Kai-Heng Feng
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=20230309201705.GA1165139@bhelgaas \
--to=helgaas@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=koba.ko@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).