| Message ID | 20240830192807.615867-1-aleksandr.loktionov@intel.com (mailing list archive) |
|---|---|
| State | Awaiting Upstream |
| Delegated to: | Netdev Maintainers |
| Headers | show |
| Series | [iwl-next,v3] i40e: add ability to reset vf for tx and rx mdd events | expand |
On Fri, Aug 30, 2024 at 9:28 PM Aleksandr Loktionov <aleksandr.loktionov@intel.com> wrote: > > In cases when vf sends malformed packets that are classified as > malicious, sometimes it causes tx queue to freeze. This frozen queue can be > stuck for several minutes being unusable. When mdd event occurs, there is a > posibility to perform a graceful vf reset to quickly bring vf back to > operational state. > > Currently vf iqueues are being disabled if mdd event occurs. > Add the ability to reset vf if tx or rx mdd occurs. > Add mdd events logging throttling /* avoid dmesg polution */. > Unify tx rx mdd messages formats. > > Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> > Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> > Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> > --- Thanks, we need this. ice has the same ability. Just one question about the patch: [...] > static void i40e_handle_mdd_event(struct i40e_pf *pf) > { > struct i40e_hw *hw = &pf->hw; > bool mdd_detected = false; > struct i40e_vf *vf; > u32 reg; > int i; > > - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) > + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf->state)) { OK, using test_and_clear_bit is good, but ...: [...] > > /* re-enable mdd interrupt cause */ > clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); Here the bit is cleared again. Why? > reg = rd32(hw, I40E_PFINT_ICR0_ENA); > reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; > wr32(hw, I40E_PFINT_ICR0_ENA, reg); > i40e_flush(hw); > + > + i40e_print_vfs_mdd_events(pf); > } Michal
> -----Original Message----- > From: Michal Schmidt <mschmidt@redhat.com> > Sent: Monday, September 2, 2024 3:25 PM > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com> > Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, Jan > <jan.sokolowski@intel.com>; Connolly, Padraig J > <padraig.j.connolly@intel.com> > Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3] i40e: add ability > to reset vf for tx and rx mdd events > > On Fri, Aug 30, 2024 at 9:28 PM Aleksandr Loktionov > <aleksandr.loktionov@intel.com> wrote: > > > > In cases when vf sends malformed packets that are classified as > > malicious, sometimes it causes tx queue to freeze. This frozen queue > > can be stuck for several minutes being unusable. When mdd event > > occurs, there is a posibility to perform a graceful vf reset to > > quickly bring vf back to operational state. > > > > Currently vf iqueues are being disabled if mdd event occurs. > > Add the ability to reset vf if tx or rx mdd occurs. > > Add mdd events logging throttling /* avoid dmesg polution */. > > Unify tx rx mdd messages formats. > > > > Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > > Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > > Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> > > --- > > Thanks, we need this. ice has the same ability. > Just one question about the patch: > > [...] > > static void i40e_handle_mdd_event(struct i40e_pf *pf) { > > struct i40e_hw *hw = &pf->hw; > > bool mdd_detected = false; > > struct i40e_vf *vf; > > u32 reg; > > int i; > > > > - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) > > + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf- > >state)) > > + { > > OK, using test_and_clear_bit is good, but ...: > > [...] > > > > /* re-enable mdd interrupt cause */ > > clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); > > Here the bit is cleared again. Why? > He code with clear_bit() is legacy and >7y old. So I can guess it's to avoid race condition. This patch introduced new functionality without changing legacy control flow, and has been tested in OOT driver. If you have suggestions in control flow change I'd suggest to merge this patch first and then try to refactor. What do you think? > > reg = rd32(hw, I40E_PFINT_ICR0_ENA); > > reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; > > wr32(hw, I40E_PFINT_ICR0_ENA, reg); > > i40e_flush(hw); > > + > > + i40e_print_vfs_mdd_events(pf); > > } > > Michal
> > On Fri, Aug 30, 2024 at 9:28 PM Aleksandr Loktionov > > <aleksandr.loktionov@intel.com> wrote: > > > > > > In cases when vf sends malformed packets that are classified as > > > malicious, sometimes it causes tx queue to freeze. This frozen queue > > > can be stuck for several minutes being unusable. When mdd event > > > occurs, there is a posibility to perform a graceful vf reset to > > > quickly bring vf back to operational state. > > > > > > Currently vf iqueues are being disabled if mdd event occurs. > > > Add the ability to reset vf if tx or rx mdd occurs. > > > Add mdd events logging throttling /* avoid dmesg polution */. > > > Unify tx rx mdd messages formats. > > > > > > Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > > > Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > > > Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > > Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > > Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> > > > --- > > > > Thanks, we need this. ice has the same ability. > > Just one question about the patch: > > > > [...] > > > static void i40e_handle_mdd_event(struct i40e_pf *pf) { > > > struct i40e_hw *hw = &pf->hw; > > > bool mdd_detected = false; > > > struct i40e_vf *vf; > > > u32 reg; > > > int i; > > > > > > - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) > > > + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf- > > >state)) > > > + { > > > > OK, using test_and_clear_bit is good, but ...: > > > > [...] > > > > > > /* re-enable mdd interrupt cause */ > > > clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); > > > > Here the bit is cleared again. Why? > > > He code with clear_bit() is legacy and >7y old. So I can guess it's to avoid race condition. > This patch introduced new functionality without changing legacy control flow, and has been tested in OOT driver. > If you have suggestions in control flow change I'd suggest to merge this patch first and then try to refactor. > What do you think? Doesn't matter how old the referred code is, you are touching the same bit so it's your responsibility to address this additional bit clearing... > > > > reg = rd32(hw, I40E_PFINT_ICR0_ENA); > > > reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; > > > wr32(hw, I40E_PFINT_ICR0_ENA, reg); > > > i40e_flush(hw); > > > + > > > + i40e_print_vfs_mdd_events(pf); > > > } > > > > Michal
On Fri, Aug 30, 2024 at 09:28:07PM +0200, Aleksandr Loktionov wrote: > In cases when vf sends malformed packets that are classified as > malicious, sometimes it causes tx queue to freeze. This frozen queue can be > stuck for several minutes being unusable. When mdd event occurs, there is a > posibility to perform a graceful vf reset to quickly bring vf back to > operational state. > > Currently vf iqueues are being disabled if mdd event occurs. > Add the ability to reset vf if tx or rx mdd occurs. > Add mdd events logging throttling /* avoid dmesg polution */. > Unify tx rx mdd messages formats. > > Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> > Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> > Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> > --- > v2->v3 fix compilation issue > v1->v2 fix compilation issue > --- > drivers/net/ethernet/intel/i40e/i40e.h | 4 +- > .../net/ethernet/intel/i40e/i40e_debugfs.c | 2 +- > .../net/ethernet/intel/i40e/i40e_ethtool.c | 2 + > drivers/net/ethernet/intel/i40e/i40e_main.c | 116 ++++++++++++++++-- > .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 2 +- > .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 11 +- > 6 files changed, 122 insertions(+), 15 deletions(-) > > diff --git a/drivers/net/ethernet/intel/i40e/i40e.h b/drivers/net/ethernet/intel/i40e/i40e.h > index d546567..6d6683c 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e.h > +++ b/drivers/net/ethernet/intel/i40e/i40e.h > @@ -87,6 +87,7 @@ enum i40e_state { > __I40E_SERVICE_SCHED, > __I40E_ADMINQ_EVENT_PENDING, > __I40E_MDD_EVENT_PENDING, > + __I40E_MDD_VF_PRINT_PENDING, > __I40E_VFLR_EVENT_PENDING, > __I40E_RESET_RECOVERY_PENDING, > __I40E_TIMEOUT_RECOVERY_PENDING, > @@ -190,6 +191,7 @@ enum i40e_pf_flags { > */ > I40E_FLAG_TOTAL_PORT_SHUTDOWN_ENA, > I40E_FLAG_VF_VLAN_PRUNING_ENA, > + I40E_FLAG_MDD_AUTO_RESET_VF, > I40E_PF_FLAGS_NBITS, /* must be last */ > }; > > @@ -571,7 +573,7 @@ struct i40e_pf { > int num_alloc_vfs; /* actual number of VFs allocated */ > u32 vf_aq_requests; > u32 arq_overflows; /* Not fatal, possibly indicative of problems */ > - > + unsigned long last_printed_mdd_jiffies; /* MDD message rate limit */ > /* DCBx/DCBNL capability for PF that indicates > * whether DCBx is managed by firmware or host > * based agent (LLDPAD). Also, indicates what > diff --git a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > index abf624d..6a697bf 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > +++ b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > @@ -721,7 +721,7 @@ static void i40e_dbg_dump_vf(struct i40e_pf *pf, int vf_id) > dev_info(&pf->pdev->dev, "vf %2d: VSI id=%d, seid=%d, qps=%d\n", > vf_id, vf->lan_vsi_id, vsi->seid, vf->num_queue_pairs); > dev_info(&pf->pdev->dev, " num MDD=%lld\n", > - vf->num_mdd_events); > + vf->mdd_tx_events.count + vf->mdd_rx_events.count); > } else { > dev_info(&pf->pdev->dev, "invalid VF id %d\n", vf_id); > } > diff --git a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > index 1d0d2e5..d146575 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > @@ -459,6 +459,8 @@ static const struct i40e_priv_flags i40e_gstrings_priv_flags[] = { > I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), > I40E_PRIV_FLAG("vf-vlan-pruning", > I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), > + I40E_PRIV_FLAG("mdd-auto-reset-vf", > + I40E_FLAG_MDD_AUTO_RESET_VF, 0), you don't tell us that this is implemented via priv-flag in the commit message, would be good to include info about it. > }; > > #define I40E_PRIV_FLAGS_STR_LEN ARRAY_SIZE(i40e_gstrings_priv_flags) > diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c > index cbcfada..28df3d5 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e_main.c > +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c > @@ -11189,22 +11189,102 @@ static void i40e_handle_reset_warning(struct i40e_pf *pf, bool lock_acquired) > i40e_reset_and_rebuild(pf, false, lock_acquired); > } > > +/** > + * i40e_print_vf_rx_mdd_event - print VF Rx malicious driver detect event > + * @pf: board private structure > + * @vf: pointer to the VF structure > + */ > +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, struct i40e_vf *vf) > +{ > + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver Detection events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", > + vf->mdd_rx_events.count, > + pf->hw.pf_id, > + vf->vf_id, > + vf->default_lan_addr.addr, > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : "off"); > +} > + > +/** > + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver detect event > + * @pf: board private structure > + * @vf: pointer to the VF structure > + */ > +static void i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct i40e_vf *vf) > +{ > + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver Detection events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", > + vf->mdd_tx_events.count, > + pf->hw.pf_id, > + vf->vf_id, > + vf->default_lan_addr.addr, > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : "off"); > +} Unnecesary code duplication, two functions with printing the very same statement with a single different letter. static void i40e_print_vf_mdd_event(struct i40e_pf *pf, struct i40e_vf *vf, const char *rxtx) { dev_err(&pf->pdev->dev, "%lld %s Malicious Driver Detection events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", vf->mdd_tx_events.count, rxtx, pf->hw.pf_id, vf->vf_id, vf->default_lan_addr.addr, test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : "off"); } i40e_print_vf_mdd_event(pf, vf, "Rx"); i40e_print_vf_mdd_event(pf, vf, "Tx"); > + > +/** > + * i40e_print_vfs_mdd_events - print VFs malicious driver detect event > + * @pf: pointer to the PF structure > + * > + * Called from i40e_handle_mdd_event to rate limit and print VFs MDD events. > + */ > +static void i40e_print_vfs_mdd_events(struct i40e_pf *pf) > +{ > + unsigned int i; > + > + /* check that there are pending MDD events to print */ > + if (!test_and_clear_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state)) > + return; > + > + /* VF MDD event logs are rate limited to one second intervals */ > + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies + HZ * 1)) > + return; > + > + pf->last_printed_mdd_jiffies = jiffies; why homegrown rate limiting? > + > + for (i = 0; i < pf->num_alloc_vfs; i++) { > + struct i40e_vf *vf = &pf->vf[i]; > + bool is_printed = false; > + > + /* only print Rx MDD event message if there are new events */ > + if (vf->mdd_rx_events.count != vf->mdd_rx_events.last_printed) { > + vf->mdd_rx_events.last_printed = vf->mdd_rx_events.count; > + i40e_print_vf_rx_mdd_event(pf, vf); > + is_printed = true; > + } > + > + /* only print Tx MDD event message if there are new events */ > + if (vf->mdd_tx_events.count != vf->mdd_tx_events.last_printed) { > + vf->mdd_tx_events.last_printed = vf->mdd_tx_events.count; > + i40e_print_vf_tx_mdd_event(pf, vf); > + is_printed = true; > + } > + > + if (is_printed && !test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags)) > + dev_info(&pf->pdev->dev, > + "Use PF Control I/F to re-enable the VF #%d\n", > + i); > + } > +} > + > /** > * i40e_handle_mdd_event > * @pf: pointer to the PF structure > * > * Called from the MDD irq handler to identify possibly malicious vfs > **/ > static void i40e_handle_mdd_event(struct i40e_pf *pf) > { > struct i40e_hw *hw = &pf->hw; > bool mdd_detected = false; > struct i40e_vf *vf; > u32 reg; > int i; > > - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) > + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf->state)) { > + /* Since the VF MDD event logging is rate limited, check if > + * there are pending MDD events. > + */ > + i40e_print_vfs_mdd_events(pf); > return; > + } > > /* find what triggered the MDD event */ > reg = rd32(hw, I40E_GL_MDET_TX); > @@ -11248,36 +11328,50 @@ static void i40e_handle_mdd_event(struct i40e_pf *pf) > > /* see if one of the VFs needs its hand slapped */ > for (i = 0; i < pf->num_alloc_vfs && mdd_detected; i++) { > + bool is_mdd_on_tx = false; > + bool is_mdd_on_rx = false; > + > vf = &(pf->vf[i]); > reg = rd32(hw, I40E_VP_MDET_TX(i)); > if (reg & I40E_VP_MDET_TX_VALID_MASK) { > + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); > wr32(hw, I40E_VP_MDET_TX(i), 0xFFFF); > - vf->num_mdd_events++; > - dev_info(&pf->pdev->dev, "TX driver issue detected on VF %d\n", > - i); > - dev_info(&pf->pdev->dev, > - "Use PF Control I/F to re-enable the VF\n"); > + vf->mdd_tx_events.count++; > set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); > + is_mdd_on_tx = true; > } > > reg = rd32(hw, I40E_VP_MDET_RX(i)); > if (reg & I40E_VP_MDET_RX_VALID_MASK) { > + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); > wr32(hw, I40E_VP_MDET_RX(i), 0xFFFF); > - vf->num_mdd_events++; > - dev_info(&pf->pdev->dev, "RX driver issue detected on VF %d\n", > - i); > - dev_info(&pf->pdev->dev, > - "Use PF Control I/F to re-enable the VF\n"); > + vf->mdd_rx_events.count++; > set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); > + is_mdd_on_rx = true; > + } > + > + if ((is_mdd_on_tx || is_mdd_on_rx) && > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags)) { > + /* VF MDD event counters will be cleared by > + * reset, so print the event prior to reset. > + */ > + if (is_mdd_on_rx) > + i40e_print_vf_rx_mdd_event(pf, vf); > + if (is_mdd_on_tx) > + i40e_print_vf_tx_mdd_event(pf, vf); > + > + i40e_vc_reset_vf(vf, true); > } > } > > /* re-enable mdd interrupt cause */ > clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); > reg = rd32(hw, I40E_PFINT_ICR0_ENA); > reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; > wr32(hw, I40E_PFINT_ICR0_ENA, reg); > i40e_flush(hw); > + > + i40e_print_vfs_mdd_events(pf); > } > > /** > diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > index 662622f..5b4618e 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > @@ -216,7 +216,7 @@ void i40e_vc_notify_vf_reset(struct i40e_vf *vf) > * @notify_vf: notify vf about reset or not > * Reset VF handler. > **/ > -static void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) > +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) > { > struct i40e_pf *pf = vf->pf; > int i; > diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > index 66f95e2..5cf74f1 100644 > --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > @@ -64,6 +64,12 @@ struct i40evf_channel { > u64 max_tx_rate; /* bandwidth rate allocation for VSIs */ > }; > > +struct i40e_mdd_vf_events { > + u64 count; /* total count of Rx|Tx events */ > + /* count number of the last printed event */ > + u64 last_printed; > +}; > + > /* VF information structure */ > struct i40e_vf { > struct i40e_pf *pf; > @@ -92,7 +98,9 @@ struct i40e_vf { > > u8 num_queue_pairs; /* num of qps assigned to VF vsis */ > u8 num_req_queues; /* num of requested qps */ > - u64 num_mdd_events; /* num of mdd events detected */ > + /* num of mdd tx and rx events detected */ > + struct i40e_mdd_vf_events mdd_rx_events; > + struct i40e_mdd_vf_events mdd_tx_events; > > unsigned long vf_caps; /* vf's adv. capabilities */ > unsigned long vf_states; /* vf's runtime states */ > @@ -120,6 +128,7 @@ int i40e_alloc_vfs(struct i40e_pf *pf, u16 num_alloc_vfs); > int i40e_vc_process_vf_msg(struct i40e_pf *pf, s16 vf_id, u32 v_opcode, > u32 v_retval, u8 *msg, u16 msglen); > int i40e_vc_process_vflr_event(struct i40e_pf *pf); > +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf); > bool i40e_reset_vf(struct i40e_vf *vf, bool flr); > bool i40e_reset_all_vfs(struct i40e_pf *pf, bool flr); > void i40e_vc_notify_vf_reset(struct i40e_vf *vf); > -- > 2.25.1 > >
> -----Original Message----- > From: Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > Sent: Tuesday, September 3, 2024 9:59 PM > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com> > Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, Jan > <jan.sokolowski@intel.com>; Connolly, Padraig J > <padraig.j.connolly@intel.com> > Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf for tx > and rx mdd events > > On Fri, Aug 30, 2024 at 09:28:07PM +0200, Aleksandr Loktionov wrote: > > In cases when vf sends malformed packets that are classified as > > malicious, sometimes it causes tx queue to freeze. This frozen queue > > can be stuck for several minutes being unusable. When mdd event > > occurs, there is a posibility to perform a graceful vf reset to > > quickly bring vf back to operational state. > > > > Currently vf iqueues are being disabled if mdd event occurs. > > Add the ability to reset vf if tx or rx mdd occurs. > > Add mdd events logging throttling /* avoid dmesg polution */. > > Unify tx rx mdd messages formats. > > > > Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > > Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > > Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> > > Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> > > --- > > v2->v3 fix compilation issue > > v1->v2 fix compilation issue > > --- > > drivers/net/ethernet/intel/i40e/i40e.h | 4 +- > > .../net/ethernet/intel/i40e/i40e_debugfs.c | 2 +- > > .../net/ethernet/intel/i40e/i40e_ethtool.c | 2 + > > drivers/net/ethernet/intel/i40e/i40e_main.c | 116 > ++++++++++++++++-- > > .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 2 +- > > .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 11 +- > > 6 files changed, 122 insertions(+), 15 deletions(-) > > > > diff --git a/drivers/net/ethernet/intel/i40e/i40e.h > > b/drivers/net/ethernet/intel/i40e/i40e.h > > index d546567..6d6683c 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e.h > > +++ b/drivers/net/ethernet/intel/i40e/i40e.h > > @@ -87,6 +87,7 @@ enum i40e_state { > > __I40E_SERVICE_SCHED, > > __I40E_ADMINQ_EVENT_PENDING, > > __I40E_MDD_EVENT_PENDING, > > + __I40E_MDD_VF_PRINT_PENDING, > > __I40E_VFLR_EVENT_PENDING, > > __I40E_RESET_RECOVERY_PENDING, > > __I40E_TIMEOUT_RECOVERY_PENDING, > > @@ -190,6 +191,7 @@ enum i40e_pf_flags { > > */ > > I40E_FLAG_TOTAL_PORT_SHUTDOWN_ENA, > > I40E_FLAG_VF_VLAN_PRUNING_ENA, > > + I40E_FLAG_MDD_AUTO_RESET_VF, > > I40E_PF_FLAGS_NBITS, /* must be last */ > > }; > > > > @@ -571,7 +573,7 @@ struct i40e_pf { > > int num_alloc_vfs; /* actual number of VFs allocated */ > > u32 vf_aq_requests; > > u32 arq_overflows; /* Not fatal, possibly indicative of problems > */ > > - > > + unsigned long last_printed_mdd_jiffies; /* MDD message rate > limit */ > > /* DCBx/DCBNL capability for PF that indicates > > * whether DCBx is managed by firmware or host > > * based agent (LLDPAD). Also, indicates what diff --git > > a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > > b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > > index abf624d..6a697bf 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > > +++ b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c > > @@ -721,7 +721,7 @@ static void i40e_dbg_dump_vf(struct i40e_pf *pf, > int vf_id) > > dev_info(&pf->pdev->dev, "vf %2d: VSI id=%d, seid=%d, > qps=%d\n", > > vf_id, vf->lan_vsi_id, vsi->seid, vf- > >num_queue_pairs); > > dev_info(&pf->pdev->dev, " num MDD=%lld\n", > > - vf->num_mdd_events); > > + vf->mdd_tx_events.count + vf- > >mdd_rx_events.count); > > } else { > > dev_info(&pf->pdev->dev, "invalid VF id %d\n", vf_id); > > } > > diff --git a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > index 1d0d2e5..d146575 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > @@ -459,6 +459,8 @@ static const struct i40e_priv_flags > i40e_gstrings_priv_flags[] = { > > I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), > > I40E_PRIV_FLAG("vf-vlan-pruning", > > I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), > > + I40E_PRIV_FLAG("mdd-auto-reset-vf", > > + I40E_FLAG_MDD_AUTO_RESET_VF, 0), > > you don't tell us that this is implemented via priv-flag in the commit > message, would be good to include info about it. This flag is implemented for other network adapters like ice, we thought it's kind of standard. Can you suggest what exact part to change? Please be concrete. Thank you > > }; > > > > #define I40E_PRIV_FLAGS_STR_LEN > ARRAY_SIZE(i40e_gstrings_priv_flags) > > diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c > > b/drivers/net/ethernet/intel/i40e/i40e_main.c > > index cbcfada..28df3d5 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e_main.c > > +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c > > @@ -11189,22 +11189,102 @@ static void > i40e_handle_reset_warning(struct i40e_pf *pf, bool lock_acquired) > > i40e_reset_and_rebuild(pf, false, lock_acquired); } > > > > +/** > > + * i40e_print_vf_rx_mdd_event - print VF Rx malicious driver detect > > +event > > + * @pf: board private structure > > + * @vf: pointer to the VF structure > > + */ > > +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, struct > > +i40e_vf *vf) { > > + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver Detection > events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", > > + vf->mdd_rx_events.count, > > + pf->hw.pf_id, > > + vf->vf_id, > > + vf->default_lan_addr.addr, > > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : > "off"); } > > + > > +/** > > + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver detect > > +event > > + * @pf: board private structure > > + * @vf: pointer to the VF structure > > + */ > > +static void i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct > > +i40e_vf *vf) { > > + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver Detection > events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", > > + vf->mdd_tx_events.count, > > + pf->hw.pf_id, > > + vf->vf_id, > > + vf->default_lan_addr.addr, > > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : > "off"); } > > Unnecesary code duplication, two functions with printing the very same > statement with a single different letter. But it's easy to grep and find as required by linux coding standards. > > static void i40e_print_vf_mdd_event(struct i40e_pf *pf, struct i40e_vf > *vf, const char *rxtx) { > dev_err(&pf->pdev->dev, "%lld %s Malicious Driver Detection > events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", > vf->mdd_tx_events.count, > rxtx, > pf->hw.pf_id, > vf->vf_id, > vf->default_lan_addr.addr, > test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : > "off"); } > > i40e_print_vf_mdd_event(pf, vf, "Rx"); > i40e_print_vf_mdd_event(pf, vf, "Tx"); > > > + > > +/** > > + * i40e_print_vfs_mdd_events - print VFs malicious driver detect > > +event > > + * @pf: pointer to the PF structure > > + * > > + * Called from i40e_handle_mdd_event to rate limit and print VFs > MDD events. > > + */ > > +static void i40e_print_vfs_mdd_events(struct i40e_pf *pf) { > > + unsigned int i; > > + > > + /* check that there are pending MDD events to print */ > > + if (!test_and_clear_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state)) > > + return; > > + > > + /* VF MDD event logs are rate limited to one second intervals */ > > + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies + HZ * > 1)) > > + return; > > + > > + pf->last_printed_mdd_jiffies = jiffies; > > why homegrown rate limiting? Because it works! And other ideas probably didn't. What is your suggestion exactly? Please be concrete. > > > + > > + for (i = 0; i < pf->num_alloc_vfs; i++) { > > + struct i40e_vf *vf = &pf->vf[i]; > > + bool is_printed = false; > > + > > + /* only print Rx MDD event message if there are new events > */ > > + if (vf->mdd_rx_events.count != vf- > >mdd_rx_events.last_printed) { > > + vf->mdd_rx_events.last_printed = vf- > >mdd_rx_events.count; > > + i40e_print_vf_rx_mdd_event(pf, vf); > > + is_printed = true; > > + } > > + > > + /* only print Tx MDD event message if there are new events > */ > > + if (vf->mdd_tx_events.count != vf- > >mdd_tx_events.last_printed) { > > + vf->mdd_tx_events.last_printed = vf- > >mdd_tx_events.count; > > + i40e_print_vf_tx_mdd_event(pf, vf); > > + is_printed = true; > > + } > > + > > + if (is_printed && !test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, > pf->flags)) > > + dev_info(&pf->pdev->dev, > > + "Use PF Control I/F to re-enable the VF > #%d\n", > > + i); > > + } > > +} > > + > > /** > > * i40e_handle_mdd_event > > * @pf: pointer to the PF structure > > * > > * Called from the MDD irq handler to identify possibly malicious > vfs > > **/ > > static void i40e_handle_mdd_event(struct i40e_pf *pf) { > > struct i40e_hw *hw = &pf->hw; > > bool mdd_detected = false; > > struct i40e_vf *vf; > > u32 reg; > > int i; > > > > - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) > > + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf->state)) { > > + /* Since the VF MDD event logging is rate limited, check > if > > + * there are pending MDD events. > > + */ > > + i40e_print_vfs_mdd_events(pf); > > return; > > + } > > > > /* find what triggered the MDD event */ > > reg = rd32(hw, I40E_GL_MDET_TX); > > @@ -11248,36 +11328,50 @@ static void i40e_handle_mdd_event(struct > > i40e_pf *pf) > > > > /* see if one of the VFs needs its hand slapped */ > > for (i = 0; i < pf->num_alloc_vfs && mdd_detected; i++) { > > + bool is_mdd_on_tx = false; > > + bool is_mdd_on_rx = false; > > + > > vf = &(pf->vf[i]); > > reg = rd32(hw, I40E_VP_MDET_TX(i)); > > if (reg & I40E_VP_MDET_TX_VALID_MASK) { > > + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); > > wr32(hw, I40E_VP_MDET_TX(i), 0xFFFF); > > - vf->num_mdd_events++; > > - dev_info(&pf->pdev->dev, "TX driver issue detected > on VF %d\n", > > - i); > > - dev_info(&pf->pdev->dev, > > - "Use PF Control I/F to re-enable the VF\n"); > > + vf->mdd_tx_events.count++; > > set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); > > + is_mdd_on_tx = true; > > } > > > > reg = rd32(hw, I40E_VP_MDET_RX(i)); > > if (reg & I40E_VP_MDET_RX_VALID_MASK) { > > + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); > > wr32(hw, I40E_VP_MDET_RX(i), 0xFFFF); > > - vf->num_mdd_events++; > > - dev_info(&pf->pdev->dev, "RX driver issue detected > on VF %d\n", > > - i); > > - dev_info(&pf->pdev->dev, > > - "Use PF Control I/F to re-enable the VF\n"); > > + vf->mdd_rx_events.count++; > > set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); > > + is_mdd_on_rx = true; > > + } > > + > > + if ((is_mdd_on_tx || is_mdd_on_rx) && > > + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags)) { > > + /* VF MDD event counters will be cleared by > > + * reset, so print the event prior to reset. > > + */ > > + if (is_mdd_on_rx) > > + i40e_print_vf_rx_mdd_event(pf, vf); > > + if (is_mdd_on_tx) > > + i40e_print_vf_tx_mdd_event(pf, vf); > > + > > + i40e_vc_reset_vf(vf, true); > > } > > } > > > > /* re-enable mdd interrupt cause */ > > clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); > > reg = rd32(hw, I40E_PFINT_ICR0_ENA); > > reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; > > wr32(hw, I40E_PFINT_ICR0_ENA, reg); > > i40e_flush(hw); > > + > > + i40e_print_vfs_mdd_events(pf); > > } > > > > /** > > diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > > b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > > index 662622f..5b4618e 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > > +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c > > @@ -216,7 +216,7 @@ void i40e_vc_notify_vf_reset(struct i40e_vf *vf) > > * @notify_vf: notify vf about reset or not > > * Reset VF handler. > > **/ > > -static void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) > > +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) > > { > > struct i40e_pf *pf = vf->pf; > > int i; > > diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > > b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > > index 66f95e2..5cf74f1 100644 > > --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > > +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h > > @@ -64,6 +64,12 @@ struct i40evf_channel { > > u64 max_tx_rate; /* bandwidth rate allocation for VSIs */ }; > > > > +struct i40e_mdd_vf_events { > > + u64 count; /* total count of Rx|Tx events */ > > + /* count number of the last printed event */ > > + u64 last_printed; > > +}; > > + > > /* VF information structure */ > > struct i40e_vf { > > struct i40e_pf *pf; > > @@ -92,7 +98,9 @@ struct i40e_vf { > > > > u8 num_queue_pairs; /* num of qps assigned to VF vsis */ > > u8 num_req_queues; /* num of requested qps */ > > - u64 num_mdd_events; /* num of mdd events detected */ > > + /* num of mdd tx and rx events detected */ > > + struct i40e_mdd_vf_events mdd_rx_events; > > + struct i40e_mdd_vf_events mdd_tx_events; > > > > unsigned long vf_caps; /* vf's adv. capabilities */ > > unsigned long vf_states; /* vf's runtime states */ > > @@ -120,6 +128,7 @@ int i40e_alloc_vfs(struct i40e_pf *pf, u16 > > num_alloc_vfs); int i40e_vc_process_vf_msg(struct i40e_pf *pf, s16 > vf_id, u32 v_opcode, > > u32 v_retval, u8 *msg, u16 msglen); int > > i40e_vc_process_vflr_event(struct i40e_pf *pf); > > +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf); > > bool i40e_reset_vf(struct i40e_vf *vf, bool flr); bool > > i40e_reset_all_vfs(struct i40e_pf *pf, bool flr); void > > i40e_vc_notify_vf_reset(struct i40e_vf *vf); > > -- > > 2.25.1 > > > >
On 9/10/24 10:29, Loktionov, Aleksandr wrote: >> From: Fijalkowski, Maciej <maciej.fijalkowski@intel.com> >> Sent: Tuesday, September 3, 2024 9:59 PM >> To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com> >> Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L >> <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, Jan >> <jan.sokolowski@intel.com>; Connolly, Padraig J >> <padraig.j.connolly@intel.com> >> Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf for tx >> and rx mdd events please capitalize acronyms (Tx, Rx, VF, MDD, PF) (also in the subject line, but sent next version as v4). >> >> On Fri, Aug 30, 2024 at 09:28:07PM +0200, Aleksandr Loktionov wrote: >>> In cases when vf sends malformed packets that are classified as >>> malicious, sometimes it causes tx queue to freeze. This frozen queue >>> can be stuck for several minutes being unusable. When mdd event >>> occurs, there is a posibility to perform a graceful vf reset to >>> quickly bring vf back to operational state. >>> >>> Currently vf iqueues are being disabled if mdd event occurs. >>> Add the ability to reset vf if tx or rx mdd occurs. >>> Add mdd events logging throttling /* avoid dmesg polution */. >>> Unify tx rx mdd messages formats. >>> >>> Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> >>> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> >>> Co-developed-by: Padraig J Connolly <padraig.j.connolly@intel.com> >>> Signed-off-by: Padraig J Connolly <padraig.j.connolly@intel.com> >>> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> Next time please wait for review on our internal e1000-mailing-list. Feel free to ping me directly if there will be no one engaged in any future series of yours. >>> --- >>> v2->v3 fix compilation issue >>> v1->v2 fix compilation issue >>> --- >>> drivers/net/ethernet/intel/i40e/i40e.h | 4 +- >>> .../net/ethernet/intel/i40e/i40e_debugfs.c | 2 +- >>> .../net/ethernet/intel/i40e/i40e_ethtool.c | 2 + >>> drivers/net/ethernet/intel/i40e/i40e_main.c | 116 >> ++++++++++++++++-- >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 2 +- >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 11 +- >>> 6 files changed, 122 insertions(+), 15 deletions(-) >>> >>> --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c >>> +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c >>> @@ -459,6 +459,8 @@ static const struct i40e_priv_flags >> i40e_gstrings_priv_flags[] = { >>> I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), >>> I40E_PRIV_FLAG("vf-vlan-pruning", >>> I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), >>> + I40E_PRIV_FLAG("mdd-auto-reset-vf", >>> + I40E_FLAG_MDD_AUTO_RESET_VF, 0), >> >> you don't tell us that this is implemented via priv-flag in the commit >> message, would be good to include info about it. > This flag is implemented for other network adapters like ice, we thought it's kind of standard. > Can you suggest what exact part to change? Please be concrete. > Thank you priv-flag is not a standard, by definition what we do in intel drivers is also not necessarily a standard keeping the code quality as-is should be rather seen as an allowance for legacy drivers, instead of something that should be copy-pasted yet again. But commit messages are different, you need to obey the current standard, which is simply: describe non-obvious things, describe more if asked during review. Please do so :) >>> +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, struct >>> +i40e_vf *vf) { >>> + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver Detection >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", >>> + vf->mdd_rx_events.count, >>> + pf->hw.pf_id, >>> + vf->vf_id, >>> + vf->default_lan_addr.addr, >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : >> "off"); } >>> + >>> +/** >>> + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver detect >>> +event >>> + * @pf: board private structure >>> + * @vf: pointer to the VF structure >>> + */ >>> +static void i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct >>> +i40e_vf *vf) { >>> + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver Detection >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", >>> + vf->mdd_tx_events.count, >>> + pf->hw.pf_id, >>> + vf->vf_id, >>> + vf->default_lan_addr.addr, >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : >> "off"); } >> >> Unnecesary code duplication, two functions with printing the very same >> statement with a single different letter. > But it's easy to grep and find as required by linux coding standards. You could reword to have it still obvious what to grep for, like: Malicious Driver Detected an Event, PF: %d, VF: %d, MAC: %pm, dir: %s... with the last %s being "Tx" or "Rx" (note: I didn't copied all your stuff as this is just an example) >>> + >>> + /* VF MDD event logs are rate limited to one second intervals */ >>> + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies + HZ * >> 1)) >>> + return; >>> + >>> + pf->last_printed_mdd_jiffies = jiffies; >> >> why homegrown rate limiting? > Because it works! And other ideas probably didn't. > What is your suggestion exactly? Please be concrete. dev_info_ratelimited()
> -----Original Message----- > From: Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com> > Sent: Tuesday, September 10, 2024 1:11 PM > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com>; > Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, > Jan <jan.sokolowski@intel.com>; Connolly, Padraig J > <padraig.j.connolly@intel.com> > Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf for > tx and rx mdd events > > On 9/10/24 10:29, Loktionov, Aleksandr wrote: > >> From: Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > >> Sent: Tuesday, September 3, 2024 9:59 PM > >> To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com> > >> Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > >> <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; > Sokolowski, Jan > >> <jan.sokolowski@intel.com>; Connolly, Padraig J > >> <padraig.j.connolly@intel.com> > >> Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf > for tx > >> and rx mdd events > > please capitalize acronyms (Tx, Rx, VF, MDD, PF) (also in the > subject line, but sent next version as v4). > > >> > >> On Fri, Aug 30, 2024 at 09:28:07PM +0200, Aleksandr Loktionov > wrote: > >>> In cases when vf sends malformed packets that are classified as > >>> malicious, sometimes it causes tx queue to freeze. This frozen > queue > >>> can be stuck for several minutes being unusable. When mdd event > >>> occurs, there is a posibility to perform a graceful vf reset to > >>> quickly bring vf back to operational state. > >>> > >>> Currently vf iqueues are being disabled if mdd event occurs. > >>> Add the ability to reset vf if tx or rx mdd occurs. > >>> Add mdd events logging throttling /* avoid dmesg polution */. > >>> Unify tx rx mdd messages formats. > >>> > >>> Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > >>> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > >>> Co-developed-by: Padraig J Connolly > <padraig.j.connolly@intel.com> > >>> Signed-off-by: Padraig J Connolly > <padraig.j.connolly@intel.com> > >>> Signed-off-by: Aleksandr Loktionov > <aleksandr.loktionov@intel.com> > > Next time please wait for review on our internal e1000-mailing- > list. > Feel free to ping me directly if there will be no one engaged in > any future series of yours. > > >>> --- > >>> v2->v3 fix compilation issue > >>> v1->v2 fix compilation issue > >>> --- > >>> drivers/net/ethernet/intel/i40e/i40e.h | 4 +- > >>> .../net/ethernet/intel/i40e/i40e_debugfs.c | 2 +- > >>> .../net/ethernet/intel/i40e/i40e_ethtool.c | 2 + > >>> drivers/net/ethernet/intel/i40e/i40e_main.c | 116 > >> ++++++++++++++++-- > >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 2 +- > >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 11 +- > >>> 6 files changed, 122 insertions(+), 15 deletions(-) > >>> > > > >>> --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > >>> +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > >>> @@ -459,6 +459,8 @@ static const struct i40e_priv_flags > >> i40e_gstrings_priv_flags[] = { > >>> I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), > >>> I40E_PRIV_FLAG("vf-vlan-pruning", > >>> I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), > >>> + I40E_PRIV_FLAG("mdd-auto-reset-vf", > >>> + I40E_FLAG_MDD_AUTO_RESET_VF, 0), > >> > >> you don't tell us that this is implemented via priv-flag in the > >> commit message, would be good to include info about it. > > This flag is implemented for other network adapters like ice, we > thought it's kind of standard. > > Can you suggest what exact part to change? Please be concrete. > > Thank you > > priv-flag is not a standard, by definition what we do in intel > drivers is also not necessarily a standard > > keeping the code quality as-is should be rather seen as an > allowance for legacy drivers, instead of something that should be > copy-pasted yet again. But commit messages are different, you need > to obey the current standard, which is simply: describe non-obvious > things, describe more if asked during review. Please do so :) > > >>> +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, > struct > >>> +i40e_vf *vf) { > >>> + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver Detection > >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset- > vfs=%s\n", > >>> + vf->mdd_rx_events.count, > >>> + pf->hw.pf_id, > >>> + vf->vf_id, > >>> + vf->default_lan_addr.addr, > >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" > : > >> "off"); } > >>> + > >>> +/** > >>> + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver > detect > >>> +event > >>> + * @pf: board private structure > >>> + * @vf: pointer to the VF structure */ static void > >>> +i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct i40e_vf > *vf) > >>> +{ > >>> + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver Detection > >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset- > vfs=%s\n", > >>> + vf->mdd_tx_events.count, > >>> + pf->hw.pf_id, > >>> + vf->vf_id, > >>> + vf->default_lan_addr.addr, > >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" > : > >> "off"); } > >> > >> Unnecesary code duplication, two functions with printing the > very > >> same statement with a single different letter. > > But it's easy to grep and find as required by linux coding > standards. > > You could reword to have it still obvious what to grep for, like: > > Malicious Driver Detected an Event, PF: %d, VF: %d, MAC: %pm, dir: > %s... > > with the last %s being "Tx" or "Rx" > (note: I didn't copied all your stuff as this is just an example) > > >>> + > >>> + /* VF MDD event logs are rate limited to one second intervals > */ > >>> + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies + HZ * > >> 1)) > >>> + return; > >>> + > >>> + pf->last_printed_mdd_jiffies = jiffies; > >> > >> why homegrown rate limiting? > > Because it works! And other ideas probably didn't. > > What is your suggestion exactly? Please be concrete. > > dev_info_ratelimited() It doesn't fit requirements. We need custom rate limiting because it needs to be re-set after each HW reset for example.
> -----Original Message----- > From: Loktionov, Aleksandr > Sent: Thursday, October 17, 2024 12:02 PM > To: Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com>; > Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, > Jan <jan.sokolowski@intel.com>; Connolly, Padraig J > <Padraig.J.Connolly@intel.com> > Subject: RE: [PATCH iwl-next v3] i40e: add ability to reset vf for > tx and rx mdd events > > > > > -----Original Message----- > > From: Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com> > > Sent: Tuesday, September 10, 2024 1:11 PM > > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com>; > > Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > > Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > > <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; Sokolowski, > > Jan <jan.sokolowski@intel.com>; Connolly, Padraig J > > <padraig.j.connolly@intel.com> > > Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf > for > > tx and rx mdd events > > > > On 9/10/24 10:29, Loktionov, Aleksandr wrote: > > >> From: Fijalkowski, Maciej <maciej.fijalkowski@intel.com> > > >> Sent: Tuesday, September 3, 2024 9:59 PM > > >> To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com> > > >> Cc: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L > > >> <anthony.l.nguyen@intel.com>; netdev@vger.kernel.org; > > Sokolowski, Jan > > >> <jan.sokolowski@intel.com>; Connolly, Padraig J > > >> <padraig.j.connolly@intel.com> > > >> Subject: Re: [PATCH iwl-next v3] i40e: add ability to reset vf > > for tx > > >> and rx mdd events > > > > please capitalize acronyms (Tx, Rx, VF, MDD, PF) (also in the > > subject line, but sent next version as v4). > > > > >> > > >> On Fri, Aug 30, 2024 at 09:28:07PM +0200, Aleksandr Loktionov > > wrote: > > >>> In cases when vf sends malformed packets that are classified > as > > >>> malicious, sometimes it causes tx queue to freeze. This > frozen > > queue > > >>> can be stuck for several minutes being unusable. When mdd > event > > >>> occurs, there is a posibility to perform a graceful vf reset > to > > >>> quickly bring vf back to operational state. > > >>> > > >>> Currently vf iqueues are being disabled if mdd event occurs. > > >>> Add the ability to reset vf if tx or rx mdd occurs. > > >>> Add mdd events logging throttling /* avoid dmesg polution */. > > >>> Unify tx rx mdd messages formats. > > >>> > > >>> Co-developed-by: Jan Sokolowski <jan.sokolowski@intel.com> > > >>> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com> > > >>> Co-developed-by: Padraig J Connolly > > <padraig.j.connolly@intel.com> > > >>> Signed-off-by: Padraig J Connolly > > <padraig.j.connolly@intel.com> > > >>> Signed-off-by: Aleksandr Loktionov > > <aleksandr.loktionov@intel.com> > > > > Next time please wait for review on our internal e1000-mailing- > > list. > > Feel free to ping me directly if there will be no one engaged in > > any future series of yours. > > > > >>> --- > > >>> v2->v3 fix compilation issue > > >>> v1->v2 fix compilation issue > > >>> --- > > >>> drivers/net/ethernet/intel/i40e/i40e.h | 4 +- > > >>> .../net/ethernet/intel/i40e/i40e_debugfs.c | 2 +- > > >>> .../net/ethernet/intel/i40e/i40e_ethtool.c | 2 + > > >>> drivers/net/ethernet/intel/i40e/i40e_main.c | 116 > > >> ++++++++++++++++-- > > >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 2 +- > > >>> .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 11 +- > > >>> 6 files changed, 122 insertions(+), 15 deletions(-) > > >>> > > > > > > >>> --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > >>> +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c > > >>> @@ -459,6 +459,8 @@ static const struct i40e_priv_flags > > >> i40e_gstrings_priv_flags[] = { > > >>> I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), > > >>> I40E_PRIV_FLAG("vf-vlan-pruning", > > >>> I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), > > >>> + I40E_PRIV_FLAG("mdd-auto-reset-vf", > > >>> + I40E_FLAG_MDD_AUTO_RESET_VF, 0), > > >> > > >> you don't tell us that this is implemented via priv-flag in > the > > >> commit message, would be good to include info about it. > > > This flag is implemented for other network adapters like ice, > we > > thought it's kind of standard. > > > Can you suggest what exact part to change? Please be concrete. > > > Thank you > > > > priv-flag is not a standard, by definition what we do in intel > > drivers is also not necessarily a standard > > > > keeping the code quality as-is should be rather seen as an > > allowance for legacy drivers, instead of something that should be > > copy-pasted yet again. But commit messages are different, you > need > > to obey the current standard, which is simply: describe non- > obvious > > things, describe more if asked during review. Please do so :) > > > > >>> +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, > > struct > > >>> +i40e_vf *vf) { > > >>> + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver > Detection > > >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset- > > vfs=%s\n", > > >>> + vf->mdd_rx_events.count, > > >>> + pf->hw.pf_id, > > >>> + vf->vf_id, > > >>> + vf->default_lan_addr.addr, > > >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) > ? "on" > > : > > >> "off"); } > > >>> + > > >>> +/** > > >>> + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver > > detect > > >>> +event > > >>> + * @pf: board private structure > > >>> + * @vf: pointer to the VF structure */ static void > > >>> +i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct > i40e_vf > > *vf) > > >>> +{ > > >>> + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver > Detection > > >> events detected on PF %d VF %d MAC %pm. mdd-auto-reset- > > vfs=%s\n", > > >>> + vf->mdd_tx_events.count, > > >>> + pf->hw.pf_id, > > >>> + vf->vf_id, > > >>> + vf->default_lan_addr.addr, > > >>> + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) > ? "on" > > : > > >> "off"); } > > >> > > >> Unnecesary code duplication, two functions with printing the > > very > > >> same statement with a single different letter. > > > But it's easy to grep and find as required by linux coding > > standards. > > > > You could reword to have it still obvious what to grep for, like: > > > > Malicious Driver Detected an Event, PF: %d, VF: %d, MAC: %pm, > dir: > > %s... > > > > with the last %s being "Tx" or "Rx" > > (note: I didn't copied all your stuff as this is just an example) > > > > >>> + > > >>> + /* VF MDD event logs are rate limited to one second > intervals > > */ > > >>> + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies > + HZ * > > >> 1)) > > >>> + return; > > >>> + > > >>> + pf->last_printed_mdd_jiffies = jiffies; > > >> > > >> why homegrown rate limiting? > > > Because it works! And other ideas probably didn't. > > > What is your suggestion exactly? Please be concrete. > > > > dev_info_ratelimited() It doesn't fit requirements. We need custom rate limiting, please see the code!
diff --git a/drivers/net/ethernet/intel/i40e/i40e.h b/drivers/net/ethernet/intel/i40e/i40e.h index d546567..6d6683c 100644 --- a/drivers/net/ethernet/intel/i40e/i40e.h +++ b/drivers/net/ethernet/intel/i40e/i40e.h @@ -87,6 +87,7 @@ enum i40e_state { __I40E_SERVICE_SCHED, __I40E_ADMINQ_EVENT_PENDING, __I40E_MDD_EVENT_PENDING, + __I40E_MDD_VF_PRINT_PENDING, __I40E_VFLR_EVENT_PENDING, __I40E_RESET_RECOVERY_PENDING, __I40E_TIMEOUT_RECOVERY_PENDING, @@ -190,6 +191,7 @@ enum i40e_pf_flags { */ I40E_FLAG_TOTAL_PORT_SHUTDOWN_ENA, I40E_FLAG_VF_VLAN_PRUNING_ENA, + I40E_FLAG_MDD_AUTO_RESET_VF, I40E_PF_FLAGS_NBITS, /* must be last */ }; @@ -571,7 +573,7 @@ struct i40e_pf { int num_alloc_vfs; /* actual number of VFs allocated */ u32 vf_aq_requests; u32 arq_overflows; /* Not fatal, possibly indicative of problems */ - + unsigned long last_printed_mdd_jiffies; /* MDD message rate limit */ /* DCBx/DCBNL capability for PF that indicates * whether DCBx is managed by firmware or host * based agent (LLDPAD). Also, indicates what diff --git a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c index abf624d..6a697bf 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_debugfs.c +++ b/drivers/net/ethernet/intel/i40e/i40e_debugfs.c @@ -721,7 +721,7 @@ static void i40e_dbg_dump_vf(struct i40e_pf *pf, int vf_id) dev_info(&pf->pdev->dev, "vf %2d: VSI id=%d, seid=%d, qps=%d\n", vf_id, vf->lan_vsi_id, vsi->seid, vf->num_queue_pairs); dev_info(&pf->pdev->dev, " num MDD=%lld\n", - vf->num_mdd_events); + vf->mdd_tx_events.count + vf->mdd_rx_events.count); } else { dev_info(&pf->pdev->dev, "invalid VF id %d\n", vf_id); } diff --git a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c index 1d0d2e5..d146575 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_ethtool.c +++ b/drivers/net/ethernet/intel/i40e/i40e_ethtool.c @@ -459,6 +459,8 @@ static const struct i40e_priv_flags i40e_gstrings_priv_flags[] = { I40E_PRIV_FLAG("base-r-fec", I40E_FLAG_BASE_R_FEC, 0), I40E_PRIV_FLAG("vf-vlan-pruning", I40E_FLAG_VF_VLAN_PRUNING_ENA, 0), + I40E_PRIV_FLAG("mdd-auto-reset-vf", + I40E_FLAG_MDD_AUTO_RESET_VF, 0), }; #define I40E_PRIV_FLAGS_STR_LEN ARRAY_SIZE(i40e_gstrings_priv_flags) diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c index cbcfada..28df3d5 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_main.c +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c @@ -11189,22 +11189,102 @@ static void i40e_handle_reset_warning(struct i40e_pf *pf, bool lock_acquired) i40e_reset_and_rebuild(pf, false, lock_acquired); } +/** + * i40e_print_vf_rx_mdd_event - print VF Rx malicious driver detect event + * @pf: board private structure + * @vf: pointer to the VF structure + */ +static void i40e_print_vf_rx_mdd_event(struct i40e_pf *pf, struct i40e_vf *vf) +{ + dev_err(&pf->pdev->dev, "%lld Rx Malicious Driver Detection events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", + vf->mdd_rx_events.count, + pf->hw.pf_id, + vf->vf_id, + vf->default_lan_addr.addr, + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : "off"); +} + +/** + * i40e_print_vf_tx_mdd_event - print VF Tx malicious driver detect event + * @pf: board private structure + * @vf: pointer to the VF structure + */ +static void i40e_print_vf_tx_mdd_event(struct i40e_pf *pf, struct i40e_vf *vf) +{ + dev_err(&pf->pdev->dev, "%lld Tx Malicious Driver Detection events detected on PF %d VF %d MAC %pm. mdd-auto-reset-vfs=%s\n", + vf->mdd_tx_events.count, + pf->hw.pf_id, + vf->vf_id, + vf->default_lan_addr.addr, + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags) ? "on" : "off"); +} + +/** + * i40e_print_vfs_mdd_events - print VFs malicious driver detect event + * @pf: pointer to the PF structure + * + * Called from i40e_handle_mdd_event to rate limit and print VFs MDD events. + */ +static void i40e_print_vfs_mdd_events(struct i40e_pf *pf) +{ + unsigned int i; + + /* check that there are pending MDD events to print */ + if (!test_and_clear_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state)) + return; + + /* VF MDD event logs are rate limited to one second intervals */ + if (time_is_after_jiffies(pf->last_printed_mdd_jiffies + HZ * 1)) + return; + + pf->last_printed_mdd_jiffies = jiffies; + + for (i = 0; i < pf->num_alloc_vfs; i++) { + struct i40e_vf *vf = &pf->vf[i]; + bool is_printed = false; + + /* only print Rx MDD event message if there are new events */ + if (vf->mdd_rx_events.count != vf->mdd_rx_events.last_printed) { + vf->mdd_rx_events.last_printed = vf->mdd_rx_events.count; + i40e_print_vf_rx_mdd_event(pf, vf); + is_printed = true; + } + + /* only print Tx MDD event message if there are new events */ + if (vf->mdd_tx_events.count != vf->mdd_tx_events.last_printed) { + vf->mdd_tx_events.last_printed = vf->mdd_tx_events.count; + i40e_print_vf_tx_mdd_event(pf, vf); + is_printed = true; + } + + if (is_printed && !test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags)) + dev_info(&pf->pdev->dev, + "Use PF Control I/F to re-enable the VF #%d\n", + i); + } +} + /** * i40e_handle_mdd_event * @pf: pointer to the PF structure * * Called from the MDD irq handler to identify possibly malicious vfs **/ static void i40e_handle_mdd_event(struct i40e_pf *pf) { struct i40e_hw *hw = &pf->hw; bool mdd_detected = false; struct i40e_vf *vf; u32 reg; int i; - if (!test_bit(__I40E_MDD_EVENT_PENDING, pf->state)) + if (!test_and_clear_bit(__I40E_MDD_EVENT_PENDING, pf->state)) { + /* Since the VF MDD event logging is rate limited, check if + * there are pending MDD events. + */ + i40e_print_vfs_mdd_events(pf); return; + } /* find what triggered the MDD event */ reg = rd32(hw, I40E_GL_MDET_TX); @@ -11248,36 +11328,50 @@ static void i40e_handle_mdd_event(struct i40e_pf *pf) /* see if one of the VFs needs its hand slapped */ for (i = 0; i < pf->num_alloc_vfs && mdd_detected; i++) { + bool is_mdd_on_tx = false; + bool is_mdd_on_rx = false; + vf = &(pf->vf[i]); reg = rd32(hw, I40E_VP_MDET_TX(i)); if (reg & I40E_VP_MDET_TX_VALID_MASK) { + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); wr32(hw, I40E_VP_MDET_TX(i), 0xFFFF); - vf->num_mdd_events++; - dev_info(&pf->pdev->dev, "TX driver issue detected on VF %d\n", - i); - dev_info(&pf->pdev->dev, - "Use PF Control I/F to re-enable the VF\n"); + vf->mdd_tx_events.count++; set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); + is_mdd_on_tx = true; } reg = rd32(hw, I40E_VP_MDET_RX(i)); if (reg & I40E_VP_MDET_RX_VALID_MASK) { + set_bit(__I40E_MDD_VF_PRINT_PENDING, pf->state); wr32(hw, I40E_VP_MDET_RX(i), 0xFFFF); - vf->num_mdd_events++; - dev_info(&pf->pdev->dev, "RX driver issue detected on VF %d\n", - i); - dev_info(&pf->pdev->dev, - "Use PF Control I/F to re-enable the VF\n"); + vf->mdd_rx_events.count++; set_bit(I40E_VF_STATE_DISABLED, &vf->vf_states); + is_mdd_on_rx = true; + } + + if ((is_mdd_on_tx || is_mdd_on_rx) && + test_bit(I40E_FLAG_MDD_AUTO_RESET_VF, pf->flags)) { + /* VF MDD event counters will be cleared by + * reset, so print the event prior to reset. + */ + if (is_mdd_on_rx) + i40e_print_vf_rx_mdd_event(pf, vf); + if (is_mdd_on_tx) + i40e_print_vf_tx_mdd_event(pf, vf); + + i40e_vc_reset_vf(vf, true); } } /* re-enable mdd interrupt cause */ clear_bit(__I40E_MDD_EVENT_PENDING, pf->state); reg = rd32(hw, I40E_PFINT_ICR0_ENA); reg |= I40E_PFINT_ICR0_ENA_MAL_DETECT_MASK; wr32(hw, I40E_PFINT_ICR0_ENA, reg); i40e_flush(hw); + + i40e_print_vfs_mdd_events(pf); } /** diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c index 662622f..5b4618e 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c @@ -216,7 +216,7 @@ void i40e_vc_notify_vf_reset(struct i40e_vf *vf) * @notify_vf: notify vf about reset or not * Reset VF handler. **/ -static void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf) { struct i40e_pf *pf = vf->pf; int i; diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h index 66f95e2..5cf74f1 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h @@ -64,6 +64,12 @@ struct i40evf_channel { u64 max_tx_rate; /* bandwidth rate allocation for VSIs */ }; +struct i40e_mdd_vf_events { + u64 count; /* total count of Rx|Tx events */ + /* count number of the last printed event */ + u64 last_printed; +}; + /* VF information structure */ struct i40e_vf { struct i40e_pf *pf; @@ -92,7 +98,9 @@ struct i40e_vf { u8 num_queue_pairs; /* num of qps assigned to VF vsis */ u8 num_req_queues; /* num of requested qps */ - u64 num_mdd_events; /* num of mdd events detected */ + /* num of mdd tx and rx events detected */ + struct i40e_mdd_vf_events mdd_rx_events; + struct i40e_mdd_vf_events mdd_tx_events; unsigned long vf_caps; /* vf's adv. capabilities */ unsigned long vf_states; /* vf's runtime states */ @@ -120,6 +128,7 @@ int i40e_alloc_vfs(struct i40e_pf *pf, u16 num_alloc_vfs); int i40e_vc_process_vf_msg(struct i40e_pf *pf, s16 vf_id, u32 v_opcode, u32 v_retval, u8 *msg, u16 msglen); int i40e_vc_process_vflr_event(struct i40e_pf *pf); +void i40e_vc_reset_vf(struct i40e_vf *vf, bool notify_vf); bool i40e_reset_vf(struct i40e_vf *vf, bool flr); bool i40e_reset_all_vfs(struct i40e_pf *pf, bool flr); void i40e_vc_notify_vf_reset(struct i40e_vf *vf);