From: David Miller <davem@davemloft.net>
To: tanhuazhong@huawei.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
salil.mehta@huawei.com, yisen.zhuang@huawei.com,
linuxarm@huawei.com
Subject: Re: [Patch net-next 00/11] add code optimization for VF reset and some new reset feature
Date: Fri, 09 Nov 2018 16:47:51 -0800 (PST) [thread overview]
Message-ID: <20181109.164751.191496935220130040.davem@davemloft.net> (raw)
In-Reply-To: <1541772476-41478-1-git-send-email-tanhuazhong@huawei.com>
From: Huazhong Tan <tanhuazhong@huawei.com>
Date: Fri, 9 Nov 2018 22:07:45 +0800
> Currently hardware supports below reset:
> 1. VF reset: triggered by sending cmd to IMP(Integrated Management
> Processor). Only reset specific VF function and do not affect
> other PF or VF.
> 2. PF reset: triggered by sending cmd to IMP. Only reset specific PF
> and it's VF.
> 3. PF FLR: triggered by PCIe subsystem. Only reset specific PF and
> it's VF.
> 4. VF FLR: triggered by PCIe subsystem. Only reset specific VF function
> and do not affect other PF or VF.
> 5. Core reset: triggered by writing to register. Reset most hardware
> unit, such as SSU, which affects all the PF and VF.
> 6. Global reset: triggered by writing to register. Reset all hardware
> unit, which affects all the PF and VF.
> 7. IMP reset: triggered by IMU(Intelligent Management Unit) when
> IMP is not longer feeding IMU's watchdog. IMU will reload the IMP
> firmware and IMP will perform global reset after firmware reloading,
> which affects all the PF and VF.
>
> Current driver only support PF/VF reset, incomplete core and global
> reset(lacking the vf reset handling). So this patchset adds complete
> reset support in hns3 driver.
>
> Also, this patchset contains some optimization related to reset.
Series applied, thank you.
prev parent reply other threads:[~2018-11-10 0:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 14:07 [Patch net-next 00/11] add code optimization for VF reset and some new reset feature Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 01/11] net: hns3: add reset_hdev to reinit the hdev in VF's reset process Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 02/11] net: hns3: adjust " Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 03/11] net: hns3: add reset handling for VF when doing PF reset Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 04/11] net: hns3: add reset handling for VF when doing Core/Global/IMP reset Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 05/11] net: hns3: stop handling command queue while resetting VF Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 06/11] net: hns3: add error handler for hclgevf_reset() Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 07/11] net: hns3: stop napi polling when HNS3_NIC_STATE_DOWN is set Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 08/11] net: hns3: implement the IMP reset processing for PF Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 09/11] net: hns3: add PCIe FLR support " Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 10/11] net: hns3: do VF's pci re-initialization while PF doing FLR Huazhong Tan
2018-11-09 14:07 ` [Patch net-next 11/11] net: hns3: add PCIe FLR support for VF Huazhong Tan
2018-11-10 0:47 ` David Miller [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=20181109.164751.191496935220130040.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@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).