1. 14 10月, 2020 1 次提交
  2. 01 9月, 2020 1 次提交
  3. 02 7月, 2020 2 次提交
    • A
      i40e: Add support for a new feature Total Port Shutdown · d5ec9e2c
      Arkadiusz Kubalewski 提交于
      After OS requests to down a link on a physical network port, the
      traffic is no longer being processed but the physical link with
      a link partner is still established.
      
      Currently there is a feature (Link down on close) which allows
      to physically bring the link down (after OS request).
      
      With this patch new feature with similar capability is introduced:
      TOTAL_PORT_SHUTDOWN
      Allows to physically disable the link on the NIC's port.
      If enabled, (after link down request from the OS)
      no link, traffic or led activity is possible on that port.
      
      If I40E_FLAG_TOTAL_PORT_SHUTDOWN is enabled, the
      I40E_FLAG_LINK_DOWN_ON_CLOSE_ENABLED must be explicitly forced to
      true and cannot be disabled at that time.
      The functionalities are exclusive in terms of configuration, but
      they also have similar behavior (allowing to disable physical link
      of the port), with following differences:
      - LINK_DOWN_ON_CLOSE_ENABLED is configurable at host OS run-time
        and is supported by whole family of 7xx Intel Ethernet Controllers
      - TOTAL_PORT_SHUTDOWN may be enabled only before OS loads (in BIOS)
        only if motherboard's BIOS and NIC's FW has support of it
      - when LINK_DOWN_ON_CLOSE_ENABLED is used, the link is being brought
        down by sending phy_type=0 to NIC's FW
      - when TOTAL_PORT_SHUTDOWN is used, phy_type is not altered, instead
        the link is being brought down by clearing bit
        (I40E_AQ_PHY_ENABLE_LINK) in abilities field of
        i40e_aq_set_phy_config structure
      
      Introduced changes:
      - new private flag I40E_FLAG_TOTAL_PORT_SHUTDOWN for handling the
        feature
      - probe of NVM if the feature was enabled at driver's port
        initialization
      - special handling on link-down procedure to let FW physically
        shutdown the port if the feature was enabled
      Signed-off-by: NArkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
      Signed-off-by: NAleksandr Loktionov <aleksandr.loktionov@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      d5ec9e2c
    • J
      ethernet/intel: Convert fallthrough code comments · 5463fce6
      Jeff Kirsher 提交于
      Convert all the remaining 'fall through" code comments to the newer
      'fallthrough;' keyword.
      Suggested-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      5463fce6
  4. 26 6月, 2020 1 次提交
    • J
      net/intel: remove driver versions from Intel drivers · 34a2a3b8
      Jeff Kirsher 提交于
      As with other networking drivers, remove the unnecessary driver version
      from the Intel drivers. The ethtool driver information and module version
      will then report the kernel version instead.
      
      For ixgbe, i40e and ice drivers, the driver passes the driver version to
      the firmware to confirm that we are up and running.  So we now pass the
      value of UTS_RELEASE to the firmware.  This adminq call is required per
      the HAS document.  The Device then sends an indication to the BMC that the
      PF driver is present. This is done using Host NC Driver Status Indication
      in NC-SI Get Link command or via the Host Network Controller Driver Status
      Change AEN.
      
      What the BMC may do with this information is implementation-dependent, but
      this is a standard NC-SI 1.1 command we honor per the HAS.
      
      CC: Bruce Allan <bruce.w.allan@intel.com>
      CC: Jesse Brandeburg <jesse.brandeburg@intel.com>
      CC: Alek Loktionov <aleksandr.loktionov@intel.com>
      CC: Kevin Liedtke <kevin.d.liedtke@intel.com>
      CC: Aaron Rowden <aaron.f.rowden@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      Co-developed-by: NJacob Keller <jacob.e.keller@intel.com>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      34a2a3b8
  5. 19 6月, 2020 1 次提交
  6. 13 3月, 2020 1 次提交
  7. 10 12月, 2019 1 次提交
  8. 26 10月, 2019 3 次提交
  9. 23 8月, 2019 1 次提交
  10. 06 8月, 2019 3 次提交
  11. 27 6月, 2019 1 次提交
  12. 15 6月, 2019 3 次提交
  13. 05 5月, 2019 2 次提交
  14. 04 5月, 2019 3 次提交
  15. 17 4月, 2019 2 次提交
  16. 27 3月, 2019 1 次提交
  17. 23 1月, 2019 1 次提交
  18. 22 1月, 2019 2 次提交
  19. 15 11月, 2018 3 次提交
  20. 08 11月, 2018 1 次提交
  21. 26 9月, 2018 1 次提交
  22. 09 9月, 2018 1 次提交
    • J
      i40e(vf): remove i40e_ethtool_stats.h header file · 6ad96bdc
      Jacob Keller 提交于
      Essentially reverts commit 8fd75c58 ("i40e: move ethtool
      stats boiler plate code to i40e_ethtool_stats.h", 2018-08-30), and
      additionally moves the similar code in i40evf into i40evf_ethtool.c.
      
      The code was intially moved from i40e_ethtool.c into i40e_ethtool_stats.h
      as a way of better logically organizing the code. This has two problems.
      First, we can't have an inline function with variadic arguments on all
      platforms. Second, it gave the appearance that we had plans to share
      code between the i40e and i40evf drivers, due to having a near copy of
      the contents in the i40evf/i40e_ethtool_stats.h file.
      
      Patches which actually attempt to combine or share code between the i40e
      and i40evf drivers have not materialized, and are likely a ways off.
      
      Rather than fixing the one function which causes build issues, just move
      this code back into the i40e_ethtool.c and i40evf_ethtool.c files. Note
      that we also change these functions back from static inlines to just
      statics, since they're no longer in a header file.
      
      We can revisit this if/when work is done to actually attempt to share
      code between drivers. Alternatively, this stats code could be made more
      generic so that it can be shared across drivers as part of ethtool
      kernel work.
      Signed-off-by: NJacob Keller <jacob.e.keller@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6ad96bdc
  23. 31 8月, 2018 2 次提交
  24. 24 8月, 2018 1 次提交
  25. 08 8月, 2018 1 次提交
    • J
      i40e: fix i40e_add_queue_stats data pointer update · 333e2f2c
      Jacob Keller 提交于
      This function accidentally failed to update the data pointer, which
      caused the reported stats to be incorrect. Additionally, statistics
      which follow queue stats in the output would potentially read non-zeroed
      garbage data from the ethtool buffer.
      
      This occurred because the data double pointer was not dereferenced
      before incrementing the size.
      
      Additionally, make sure this issue is more visible by adding a WARN_ONCE
      to the i40e_get_ethtool_stats function. This warning will trigger
      whenever the data pointer is not at the expected address, similar to the
      check that we make in the i40e_get_stat_strings() function.
      Signed-off-by: NJacob Keller <jacob.e.keller@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      333e2f2c