1. 01 5月, 2018 1 次提交
  2. 28 4月, 2018 1 次提交
  3. 24 3月, 2018 1 次提交
  4. 24 1月, 2018 1 次提交
  5. 11 1月, 2018 1 次提交
  6. 22 11月, 2017 1 次提交
  7. 10 10月, 2017 2 次提交
  8. 06 9月, 2017 2 次提交
    • J
      i40e: point wb_desc at the nvm_wb_desc during i40e_read_nvm_aq · 3c8f3e96
      Jacob Keller 提交于
      When introducing the functions to read the NVM through the AdminQ, we
      did not correctly mark the wb_desc.
      
      Fixes: 7073f46e ("i40e: Add AQ commands for NVM Update for X722", 2015-06-05)
      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>
      3c8f3e96
    • A
      i40e: avoid NVM acquire deadlock during NVM update · 09f79fd4
      Anjali Singhai Jain 提交于
      X722 devices use the AdminQ to access the NVM, and this requires taking
      the AdminQ lock. Because of this, we lock the AdminQ during
      i40e_read_nvm(), which is also called in places where the lock is
      already held, such as the firmware update path which wants to lock once
      and then unlock when finished after performing several tasks.
      
      Although this should have only affected X722 devices, commit
      96a39aed ("i40e: Acquire NVM lock before reads on all devices",
      2016-12-02) added locking for all NVM reads, regardless of device
      family.
      
      This resulted in us accidentally causing NVM acquire timeouts on all
      devices, causing failed firmware updates which left the eeprom in
      a corrupt state.
      
      Create unsafe non-locked variants of i40e_read_nvm_word and
      i40e_read_nvm_buffer, __i40e_read_nvm_word and __i40e_read_nvm_buffer
      respectively. These variants will not take the NVM lock and are expected
      to only be called in places where the NVM lock is already held if
      needed.
      
      Since the only caller of i40e_read_nvm_buffer() was in such a path,
      remove it entirely in favor of the unsafe version. If necessary we can
      always add it back in the future.
      
      Additionally, we now need to hold the NVM lock in i40e_validate_checksum
      because the call to i40e_calc_nvm_checksum now assumes that the NVM lock
      is held. We can further move the call to read I40E_SR_SW_CHECKSUM_WORD
      up a bit so that we do not need to acquire the NVM lock twice.
      
      This should resolve firmware updates and also fix potential raise that
      could have caused the driver to report an invalid NVM checksum upon
      driver load.
      Reported-by: NStefan Assmann <sassmann@kpanic.de>
      Fixes: 96a39aed ("i40e: Acquire NVM lock before reads on all devices", 2016-12-02)
      Signed-off-by: NAnjali Singhai Jain <anjali.singhai@intel.com>
      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>
      09f79fd4
  9. 28 8月, 2017 1 次提交
  10. 26 8月, 2017 1 次提交
  11. 26 7月, 2017 1 次提交
  12. 15 3月, 2017 1 次提交
  13. 01 11月, 2016 1 次提交
  14. 27 4月, 2016 1 次提交
  15. 07 4月, 2016 2 次提交
  16. 17 2月, 2016 1 次提交
  17. 23 10月, 2015 2 次提交
  18. 20 10月, 2015 1 次提交
  19. 16 10月, 2015 1 次提交
  20. 08 10月, 2015 1 次提交
  21. 18 9月, 2015 6 次提交
  22. 06 8月, 2015 1 次提交
  23. 23 7月, 2015 1 次提交
  24. 15 4月, 2015 1 次提交
  25. 07 3月, 2015 2 次提交
  26. 26 2月, 2015 1 次提交
  27. 24 2月, 2015 1 次提交
  28. 10 12月, 2014 3 次提交