1. 01 11月, 2017 2 次提交
  2. 26 9月, 2017 1 次提交
  3. 15 8月, 2017 2 次提交
  4. 12 8月, 2017 1 次提交
  5. 07 8月, 2017 1 次提交
  6. 25 7月, 2017 1 次提交
    • P
      liquidio: fix implicit irq include causing build failures · ba3fb102
      Paul Gortmaker 提交于
      To fix
      
      In file included from drivers/net/ethernet/cavium/liquidio/octeon_mem_ops.c:24:0:
      drivers/net/ethernet/cavium/liquidio/octeon_device.h:216:2: error: expected specifier-qualifier-list before ‘irqreturn_t’
        irqreturn_t (*process_interrupt_regs)(void *);
        ^
      
      as seen on arm64 allmodconfig builds.
      
      Cc: Derek Chickles <derek.chickles@caviumnetworks.com>
      Cc: Satanand Burla <satananda.burla@caviumnetworks.com>
      Cc: Felix Manlunas <felix.manlunas@caviumnetworks.com>
      Cc: Raghu Vatsavayi <raghu.vatsavayi@caviumnetworks.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ba3fb102
  7. 18 5月, 2017 1 次提交
  8. 07 4月, 2017 1 次提交
    • F
      liquidio: fix Octeon core watchdog timeout false alarm · bb54be58
      Felix Manlunas 提交于
      Detection of watchdog timeout of Octeon cores is flawed and susceptible to
      false alarms.  Refactor by removing the detection code, and in its place,
      leverage existing code that monitors for an indication from the NIC
      firmware that an Octeon core crashed; expand the meaning of the indication
      to "an Octeon core crashed or its watchdog timer expired".  Detection of
      watchdog timeout is now delegated to an exception handler in the NIC
      firmware; this is free of false alarms.
      
      Also if there's an Octeon core crash or watchdog timeout:
      (1) Disable VF Ethernet links.
      (2) Decrement the module refcount by an amount equal to the number of
          active VFs of the NIC whose Octeon core crashed or had a watchdog
          timeout.  The refcount will continue to reflect the active VFs of
          other liquidio NIC(s) (if present) whose Octeon cores are faultless.
      
      Item (2) is needed to avoid the case of not being able to unload the driver
      because the module refcount is stuck at some non-zero number.  There is
      code that, in normal cases, decrements the refcount upon receiving a
      message from the firmware that a VF driver was unloaded.  But in
      exceptional cases like an Octeon core crash or watchdog timeout, arrival of
      that particular message from the firmware might be unreliable.  That normal
      case code is changed to not touch the refcount in the exceptional case to
      avoid contention (over the refcount) with the liquidio_watchdog kernel
      thread who will carry out item (2).
      Signed-off-by: NFelix Manlunas <felix.manlunas@cavium.com>
      Signed-off-by: NDerek Chickles <derek.chickles@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bb54be58
  9. 29 3月, 2017 1 次提交
  10. 17 3月, 2017 1 次提交
  11. 30 12月, 2016 1 次提交
  12. 01 12月, 2016 2 次提交
  13. 16 11月, 2016 8 次提交
  14. 03 9月, 2016 3 次提交
  15. 01 9月, 2016 6 次提交
  16. 05 7月, 2016 2 次提交
  17. 26 6月, 2016 5 次提交
  18. 16 6月, 2016 1 次提交