From: Leon Romanovsky <leon@kernel.org>
To: Hao Lan <lanhao@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, edumazet@google.com, pabeni@redhat.com,
richardcochran@gmail.com, shenjian15@huawei.com,
wangjie125@huawei.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: hns3: add vf fault process in hns3 ras
Date: Fri, 13 Jan 2023 08:51:33 +0200 [thread overview]
Message-ID: <Y8D/dXTBxrLOwmgc@unreal> (raw)
In-Reply-To: <20230113020829.48451-3-lanhao@huawei.com>
On Fri, Jan 13, 2023 at 10:08:29AM +0800, Hao Lan wrote:
> From: Jie Wang <wangjie125@huawei.com>
>
> Currently hns3 driver supports vf fault detect feature. Several ras caused
> by VF resources don't need to do PF function reset for recovery. The driver
> only needs to reset the specified VF.
>
> So this patch adds process in ras module. New process will get detailed
> information about ras and do the most correct measures based on these
> accurate information.
>
> Signed-off-by: Jie Wang <wangjie125@huawei.com>
> Signed-off-by: Hao Lan <lanhao@huawei.com>
> ---
> drivers/net/ethernet/hisilicon/hns3/hnae3.h | 1 +
> .../hns3/hns3_common/hclge_comm_cmd.h | 1 +
> .../hisilicon/hns3/hns3pf/hclge_err.c | 113 +++++++++++++++++-
> .../hisilicon/hns3/hns3pf/hclge_err.h | 2 +
> .../hisilicon/hns3/hns3pf/hclge_main.c | 3 +-
> .../hisilicon/hns3/hns3pf/hclge_main.h | 1 +
> 6 files changed, 115 insertions(+), 6 deletions(-)
Why is it good idea to reset VF from PF?
What will happen with driver bound to this VF?
Shouldn't PCI recovery handle it?
Thanks
next prev parent reply other threads:[~2023-01-13 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 2:08 [PATCH net-next 0/2] add some vf fault detect patch for hns Hao Lan
2023-01-13 2:08 ` [PATCH net-next 1/2] net: hns3: add hns3 vf fault detect cap bit support Hao Lan
2023-01-13 2:08 ` [PATCH net-next 2/2] net: hns3: add vf fault process in hns3 ras Hao Lan
2023-01-13 6:51 ` Leon Romanovsky [this message]
2023-01-17 7:04 ` wangjie (L)
2023-01-17 11:21 ` Leon Romanovsky
2023-01-18 12:34 ` wangjie (L)
2023-01-20 17:12 ` Leon Romanovsky
2023-01-31 12:04 ` wangjie (L)
2023-01-31 13:24 ` Leon Romanovsky
2023-02-02 13:08 ` wangjie (L)
2023-02-06 13:36 ` Leon Romanovsky
2023-01-17 8:04 ` Paolo Abeni
2023-01-18 12:36 ` wangjie (L)
2023-01-18 12:36 ` wangjie (L)
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=Y8D/dXTBxrLOwmgc@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lanhao@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@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).