linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huazhong Tan <tanhuazhong@huawei.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<salil.mehta@huawei.com>, <yisen.zhuang@huawei.com>,
	<linuxarm@huawei.com>, <jakub.kicinski@netronome.com>,
	Jian Shen <shenjian15@huawei.com>,
	"Huazhong Tan" <tanhuazhong@huawei.com>
Subject: [PATCH net-next 8/8] net: hns3: log and clear hardware error after reset complete
Date: Sat, 19 Oct 2019 16:03:56 +0800	[thread overview]
Message-ID: <1571472236-17401-9-git-send-email-tanhuazhong@huawei.com> (raw)
In-Reply-To: <1571472236-17401-1-git-send-email-tanhuazhong@huawei.com>

From: Jian Shen <shenjian15@huawei.com>

When device is resetting, the CMDQ service may be stopped until
reset completed. If a new RAS error occurs at this moment, it
will no be able to clear the RAS source. This patch fixes it
by clear the RAS source after reset complete.

Signed-off-by: Jian Shen <shenjian15@huawei.com>
Signed-off-by: Huazhong Tan <tanhuazhong@huawei.com>
---
 drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
index ffdb8ce..95c3897 100644
--- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
+++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
@@ -9781,6 +9781,9 @@ static int hclge_reset_ae_dev(struct hnae3_ae_dev *ae_dev)
 		return ret;
 	}
 
+	/* Log and clear the hw errors those already occurred */
+	hclge_handle_all_hns_hw_errors(ae_dev);
+
 	/* Re-enable the hw error interrupts because
 	 * the interrupts get disabled on global reset.
 	 */
-- 
2.7.4


  parent reply	other threads:[~2019-10-19  8:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19  8:03 [PATCH net-next 0/8] net: hns3: add some cleanups & optimizations Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 1/8] net: hns3: remove struct hns3_nic_ring_data in hns3_enet module Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 2/8] net: hns3: optimized MAC address in management table Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 3/8] net: hns3: minor optimization for barrier in IO path Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 4/8] net: hns3: introduce ring_to_netdev() in enet module Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 5/8] net: hns3: make struct hns3_enet_ring cacheline aligned Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 6/8] net: hns3: minor cleanup for hns3_handle_rx_bd() Huazhong Tan
2019-10-19  8:03 ` [PATCH net-next 7/8] net: hns3: do not allocate linear data for fraglist skb Huazhong Tan
2019-10-19  8:03 ` Huazhong Tan [this message]
2019-10-20 17:37 ` [PATCH net-next 0/8] net: hns3: add some cleanups & optimizations Jakub Kicinski
2019-10-21 16:22 ` David Miller

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=1571472236-17401-9-git-send-email-tanhuazhong@huawei.com \
    --to=tanhuazhong@huawei.com \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=yisen.zhuang@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;
as well as URLs for NNTP newsgroup(s).