patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "Min Hu (Connor)" <humin29@huawei.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 20.11] net/hns3: fix concurrent interrupt handling
Date: Sun, 13 Jun 2021 07:42:49 +0000	[thread overview]
Message-ID: <DM4PR12MB53734A4A15210C1820D1A980A1329@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1623568350-8495-1-git-send-email-humin29@huawei.com>

Applied, thanks!

> -----Original Message-----
> From: Min Hu (Connor) <humin29@huawei.com>
> Sent: Sunday, June 13, 2021 3:13 PM
> To: stable@dpdk.org
> Cc: Xueming(Steven) Li <xuemingl@nvidia.com>
> Subject: [PATCH 20.11] net/hns3: fix concurrent interrupt handling
> 
> From: Hongbo Zheng <zhenghongbo3@huawei.com>
> 
> [ upstream commit f9f24ecd794f88231110c823cdeff5d7ec9a4382 ]
> 
> Currently, if RAS interrupt and FLR occurred at the same time, FLR will be detected and corresponding schedule state will be set during
> RAS interrupt processing. However, the schedule state value will be overridden in subsequent RAS processing, resulting in FLR
> processing failure. This patch solves this problem.
> 
> Fixes: 2790c6464725 ("net/hns3: support device reset")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Hongbo Zheng <zhenghongbo3@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
>  drivers/net/hns3/hns3_intr.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/hns3/hns3_intr.c b/drivers/net/hns3/hns3_intr.c index 99b5301..0bba3ab 100644
> --- a/drivers/net/hns3/hns3_intr.c
> +++ b/drivers/net/hns3/hns3_intr.c
> @@ -1787,7 +1787,8 @@ hns3_schedule_reset(struct hns3_adapter *hns)
>  		return;
>  	if (rte_atomic16_read(&hns->hw.reset.schedule) == SCHEDULE_DEFERRED)
>  		rte_eal_alarm_cancel(hw->reset.ops->reset_service, hns);
> -	rte_atomic16_set(&hns->hw.reset.schedule, SCHEDULE_REQUESTED);
> +	else
> +		rte_atomic16_set(&hns->hw.reset.schedule, SCHEDULE_REQUESTED);
> 
>  	rte_eal_alarm_set(SWITCH_CONTEXT_US, hw->reset.ops->reset_service, hns);  }
> --
> 2.7.4


      reply	other threads:[~2021-06-13  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13  7:12 Min Hu (Connor)
2021-06-13  7:42 ` Xueming(Steven) Li [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=DM4PR12MB53734A4A15210C1820D1A980A1329@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=humin29@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).