DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Huaxing Zhu <huaxing.zhu@corigine.com>,
	Long Wu <long.wu@corigine.com>,
	Peng Zhang <peng.zhang@corigine.com>,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 4/4] net/nfp: clear errors status of aer after soft reset
Date: Mon, 14 Oct 2024 10:43:58 +0800	[thread overview]
Message-ID: <20241014024358.3873420-5-chaoyong.he@corigine.com> (raw)
In-Reply-To: <20241014024358.3873420-1-chaoyong.he@corigine.com>

From: Huaxing Zhu <huaxing.zhu@corigine.com>

Accessing device memory during soft reset may result in some
errors being recorded in PCIE's AER register, which is normal.
Therefore, after the soft reset is completed, these errors
should be cleared.

Signed-off-by: Huaxing Zhu <huaxing.zhu@corigine.com>
Reviewed-by: Long Wu <long.wu@corigine.com>
Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
---
 drivers/net/nfp/nfp_ethdev.c | 40 ++++++++++++++++++++++++++++++++++--
 1 file changed, 38 insertions(+), 2 deletions(-)

diff --git a/drivers/net/nfp/nfp_ethdev.c b/drivers/net/nfp/nfp_ethdev.c
index 8cbbadb4de..b16fbe7db7 100644
--- a/drivers/net/nfp/nfp_ethdev.c
+++ b/drivers/net/nfp/nfp_ethdev.c
@@ -1338,9 +1338,37 @@ nfp_fw_check_change(struct nfp_cpp *cpp,
 	return 0;
 }
 
+static void
+nfp_pcie_reg32_write_clear(struct rte_pci_device *pci_dev,
+		int position)
+{
+	int ret;
+	uint32_t capability;
+
+	ret = rte_pci_read_config(pci_dev, &capability, 4, position);
+	if (ret < 0)
+		capability = 0xffffffff;
+
+	(void)rte_pci_write_config(pci_dev, &capability, 4, position);
+}
+
+static void
+nfp_pcie_aer_clear(struct rte_pci_device *pci_dev)
+{
+	int pos;
+
+	pos = rte_pci_find_ext_capability(pci_dev, RTE_PCI_EXT_CAP_ID_ERR);
+	if (pos <= 0)
+		return;
+
+	nfp_pcie_reg32_write_clear(pci_dev, pos + RTE_PCI_ERR_UNCOR_STATUS);
+	nfp_pcie_reg32_write_clear(pci_dev, pos + RTE_PCI_ERR_COR_STATUS);
+}
+
 static int
 nfp_fw_reload(struct nfp_nsp *nsp,
 		char *fw_name,
+		struct rte_pci_device *pci_dev,
 		int reset)
 {
 	int err;
@@ -1357,6 +1385,14 @@ nfp_fw_reload(struct nfp_nsp *nsp,
 		}
 	}
 
+	/*
+	 * Accessing device memory during soft reset may result in some
+	 * errors being recorded in PCIE's AER register, which is normal.
+	 * Therefore, after the soft reset is completed, these errors
+	 * should be cleared.
+	 */
+	nfp_pcie_aer_clear(pci_dev);
+
 	err = nfp_fw_upload(nsp, fw_name);
 	if (err != 0) {
 		PMD_DRV_LOG(ERR, "NFP firmware load failed");
@@ -1463,7 +1499,7 @@ nfp_fw_reload_for_single_pf_from_disk(struct nfp_nsp *nsp,
 	if (!fw_changed)
 		return 0;
 
-	ret = nfp_fw_reload(nsp, fw_name, reset);
+	ret = nfp_fw_reload(nsp, fw_name, pf_dev->pci_dev, reset);
 	if (ret != 0)
 		return ret;
 
@@ -1523,7 +1559,7 @@ nfp_fw_reload_for_multi_pf_from_disk(struct nfp_nsp *nsp,
 	if (skip_load_fw && !reload_fw)
 		return 0;
 
-	err = nfp_fw_reload(nsp, fw_name, reset);
+	err = nfp_fw_reload(nsp, fw_name, pf_dev->pci_dev, reset);
 	if (err != 0)
 		return err;
 
-- 
2.39.1


  parent reply	other threads:[~2024-10-14  2:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  2:43 [PATCH 0/4] debug enhancement and bug fix Chaoyong He
2024-10-14  2:43 ` [PATCH 1/4] net/nfp: notify flower firmware about PF speed Chaoyong He
2024-10-14  2:43 ` [PATCH 2/4] net/nfp: do not set the IPv6 flag in transport mode Chaoyong He
2024-10-14  2:43 ` [PATCH 3/4] net/nfp: add more logs to debug probe process Chaoyong He
2024-10-14  2:43 ` Chaoyong He [this message]
2024-10-16 23:08 ` [PATCH 0/4] debug enhancement and bug fix Ferruh Yigit

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=20241014024358.3873420-5-chaoyong.he@corigine.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=huaxing.zhu@corigine.com \
    --cc=long.wu@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.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).