1. 21 12月, 2013 4 次提交
  2. 20 12月, 2013 1 次提交
  3. 19 12月, 2013 2 次提交
  4. 12 12月, 2013 2 次提交
  5. 11 12月, 2013 2 次提交
  6. 10 12月, 2013 1 次提交
  7. 07 12月, 2013 6 次提交
  8. 06 12月, 2013 1 次提交
  9. 03 12月, 2013 1 次提交
  10. 29 11月, 2013 1 次提交
  11. 22 11月, 2013 1 次提交
  12. 19 11月, 2013 4 次提交
  13. 15 11月, 2013 1 次提交
  14. 13 11月, 2013 1 次提交
  15. 08 11月, 2013 1 次提交
  16. 31 10月, 2013 1 次提交
  17. 30 10月, 2013 2 次提交
  18. 29 10月, 2013 2 次提交
    • A
      bnx2x: Disable VF access on PF removal · 826cb7b4
      Ariel Elior 提交于
      When the bnx2x driver is rmmoded, if VFs of a given PF will be assigned
      to a VM then that PF will be unable to call `pci_disable_sriov()'.
      
      If for that same PF there would also exist unassigned VFs in the hypervisor,
      the result will be that after the removal there will still be virtual PCI
      functions on the hypervisor.
      If the bnx2x module were to be re-inserted, the result will be that the VFs
      on the hypervisor will be re-probed directly following the PF's probe, even
      though that in regular loading flow sriov is only enabled once PF is loaded.
      The probed VF will then try to access its bar, causing a PCI error as the HW
      is not in a state enabling such a request.
      
      This patch adds a missing disablement procedure to the PF's removal, one that
      sets registers viewable to the VF to indicate that the VFs have no permission
      to access the bar, thus resulting in probe errors instead of PCI errors.
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NYuval Mintz <yuvalmin@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      826cb7b4
    • D
      bnx2x: prevent FW assert on low mem during unload · e3ed4eae
      Dmitry Kravkov 提交于
      Buffers for FW statistics were allocated at an inappropriate time; In a machine
      where the driver encounters problems allocating all of its queues, the driver
      would still create FW requests for the statistics of the non-existing queues.
      The wrong order of memory allocation could lead to zeroed statistics messages
      being sent, leading to fw assert in case function 0 was down.
      
      This changes the order of allocations, guaranteeing that statistic requests will
      only be generated for actual queues.
      Signed-off-by: NDmitry Kravkov <dmitry@broadcom.com>
      Signed-off-by: NYuval Mintz <yuvalmin@broadcom.com>
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e3ed4eae
  19. 22 10月, 2013 6 次提交