From: Kevin Traynor <ktraynor@redhat.com>
To: Dengdui Huang <huangdengdui@huawei.com>, stable@dpdk.org
Cc: liuyonglong@huawei.com
Subject: Re: [PATCH 21.11] net/hns3: fix IMP or global reset
Date: Thu, 23 Nov 2023 10:52:16 +0000 [thread overview]
Message-ID: <5a9bec54-cd4e-051e-9fc4-eb412abbd846@redhat.com> (raw)
In-Reply-To: <20231123011927.2993620-1-huangdengdui@huawei.com>
On 23/11/2023 01:19, Dengdui Huang wrote:
> [ upstream commit 1eee1ea75c0eadaea6dde368b289cf0acf6a1190 ]
>
> Currently, when the IMP or Global reset detected, the vector0
> interrupt is enabled before the reset process is completed.
> At this moment, if the initialization of IMP is not completed,
> and the vector0 interrupt may continue to be reported. In this
> scenario, the IMP/global reset being performed by the driver
> does not need to be interrupted. Therefore, for IMP and global
> resets, the driver has to enable the interrupt after the end
> of reset.
>
> The RAS interrupt is also shared with the vector0 interrupt.
> When the interrupt is disabled, the RAS interrupt can still be
> reported to the driver and the driver interrupt processing
> function is also called. In this case, the interrupt status of
> the IMP/global may still exist. Therefore, this patch also has
> to the check of the new reset level based on the priority of
> reset level in the interrupt handler.
>
> Fixes: 2790c6464725 ("net/hns3: support device reset")
> Fixes: 3988ab0eee52 ("net/hns3: add abnormal interrupt process")
> Cc:stable@dpdk.org
>
> Signed-off-by: Dengdui Huang<huangdengdui@huawei.com>
> ---
> drivers/net/hns3/hns3_ethdev.c | 88 ++++++++++++++++++++++++++++------
> drivers/net/hns3/hns3_ethdev.h | 1 +
> drivers/net/hns3/hns3_intr.c | 2 +
> 3 files changed, 77 insertions(+), 14 deletions(-)
Applied to 21.11 branch. Thanks for backporting.
prev parent reply other threads:[~2023-11-23 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 1:19 Dengdui Huang
2023-11-23 10:52 ` Kevin Traynor [this message]
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=5a9bec54-cd4e-051e-9fc4-eb412abbd846@redhat.com \
--to=ktraynor@redhat.com \
--cc=huangdengdui@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stable@dpdk.org \
/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).