1. 30 3月, 2018 1 次提交
    • M
      qed*: Utilize FW 8.33.11.0 · 50bc60cb
      Michal Kalderon 提交于
      This FW contains several fixes and features
      
      RDMA Features
      - SRQ support
      - XRC support
      - Memory window support
      - RDMA low latency queue support
      - RDMA bonding support
      
      RDMA bug fixes
      - RDMA remote invalidate during retransmit fix
      - iWARP MPA connect interop issue with RTR fix
      - iWARP Legacy DPM support
      - Fix MPA reject flow
      - iWARP error handling
      - RQ WQE validation checks
      
      MISC
      - Fix some HSI types endianity
      - New Restriction: vlan insertion in core_tx_bd_data can't be set
        for LB packets
      
      ETH
      - HW QoS offload support
      - Fix vlan, dcb and sriov flow of VF sending a packet with
        inband VLAN tag instead of default VLAN
      - Allow GRE version 1 offloads in RX flow
      - Allow VXLAN steering
      
      iSCSI / FcoE
      - Fix bd availability checking flow
      - Support 256th sge proerly in iscsi/fcoe retransmit
      - Performance improvement
      - Fix handle iSCSI command arrival with AHS and with immediate
      - Fix ipv6 traffic class configuration
      
      DEBUG
      - Update debug utilities
      Signed-off-by: NMichal Kalderon <Michal.Kalderon@cavium.com>
      Signed-off-by: NTomer Tayar <Tomer.Tayar@cavium.com>
      Signed-off-by: NManish Rangankar <Manish.Rangankar@cavium.com>
      Signed-off-by: NAriel Elior <Ariel.Elior@cavium.com>
      Acked-by: NJason Gunthorpe <jgg@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      50bc60cb
  2. 03 1月, 2018 3 次提交
  3. 27 7月, 2017 1 次提交
  4. 03 7月, 2017 1 次提交
  5. 31 5月, 2017 3 次提交
  6. 25 5月, 2017 2 次提交
  7. 19 5月, 2017 1 次提交
  8. 18 4月, 2017 1 次提交
  9. 04 4月, 2017 1 次提交
  10. 29 3月, 2017 4 次提交
    • T
      qed: Utilize resource-lock based scheme · 9c8517c4
      Tomer Tayar 提交于
      Management firmware is used as an arbiter between the various PFs
      in matters of resources, but some of the resources that need to
      be divided are dependent on the non-management firmware used,
      so management firmware first needs to be told how many resources
      there are before trying to divide them.
      
      As part of the initialization sequence, driver would first inform
      the management firmware of the available resources under
      a dedicated resource lock, and afterwards request for various
      resources which might be based on the previous set values.
      Signed-off-by: NTomer Tayar <Tomer.Tayar@cavium.com>
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9c8517c4
    • T
      qed: Support management-based resource locking · 95691c9c
      Tomer Tayar 提交于
      Global locking can't properly be used to synchronize between different
      PFs in all scenarios, as those instances might reside in different
      logical partitions [e.g., when a PF is assigned via PDA to some VM].
      
      The management firmware provides a generic infrastructure for
      device locks. For each 'resource', it's guaranteed it could be acquired
      by at most a single PF at any given time [or by management firmware].
      
      This patch adds the necessary logic in qed for utilizing said
      infrastructure, implementing lock/unlock internal APIs.
      Signed-off-by: NTomer Tayar <Tomer.Tayar@cavium.com>
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      95691c9c
    • M
      qed: Send pf-flr as part of initialization · 18a69e36
      Mintz, Yuval 提交于
      During HW initialization, driver would set various registers to their
      needed values - but it assumes all registers start at their reset-value,
      so there's no need to re-configure a register's default value.
      
      This assumption might be incorrect, e.g., in case of preboot driver
      running and initializing the driver prior to our driver.
      
      To overcome this, we now ask management firmware to initiate a PF-flr
      early during the initialization sequence. That would return everything
      in the PF's scope back to default and prevent previous configurations
      from still being applied.
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      18a69e36
    • T
      qed: Move to new load request scheme · 5d24bcf1
      Tomer Tayar 提交于
      Management firmware is used as an arbiter between the various PFs
      in regard to loading - it causes the various PFs to load/unload
      sequentially and informs each of its appropriate rule in the init.
      
      But the existing flow is too weak to handle some scenarios where
      PFs aren't properly cleaned prior to loading.
      The significant scenarios falling under this criteria:
        a. Preboot drivers in some environment can't properly unload.
        b. Unexpected driver replacement [kdump, PDA].
      
      Modern management firmware supports a more intricate loading flow,
      where the driver has the ability to overcome previous limitations.
      This moves qed into using this newer scheme.
      
      Notice new scheme is backward compatible, so new drivers would
      still be able to load properly on top of older management firmwares
      and vice versa.
      Signed-off-by: NTomer Tayar <Tomer.Tayar@cavium.com>
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5d24bcf1
  11. 15 3月, 2017 1 次提交
  12. 14 3月, 2017 1 次提交
  13. 20 2月, 2017 1 次提交
  14. 02 1月, 2017 1 次提交
  15. 11 11月, 2016 1 次提交
  16. 10 11月, 2016 1 次提交
    • M
      qed: Prevent stack corruption on MFW interaction · bb480242
      Mintz, Yuval 提交于
      Driver uses a union for copying data to & from management firmware
      when interacting with it.
      Problem is that the function always copies sizeof(union) while commit
      2edbff8d ("qed: Learn resources from management firmware") is casting
      a union elements which is of smaller size [24-byte instead of 88-bytes].
      
      Also, the union contains some inappropriate elements which increase its
      size [should have been 32-bytes]. While this shouldn't corrupt other
      PF messages to the MFW [as management firmware enforces permissions so
      that each PF is allowed to write only to its own mailbox] we fix this
      here as well.
      
      Fixes: 2edbff8d ("qed: Learn resources from management firmware")
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bb480242
  17. 01 11月, 2016 5 次提交
  18. 04 10月, 2016 1 次提交
  19. 08 9月, 2016 1 次提交
  20. 07 9月, 2016 1 次提交
  21. 20 8月, 2016 1 次提交
    • Y
      qed: utilize FW 8.10.10.0 · 05fafbfb
      Yuval Mintz 提交于
      This new firmware for the qed* adpaters fixes several issues:
       - Better blocking of malicious VFs.
       - After FLR, Tx-switching [internal routing] of packets might
         be incorrect.
       - Deletion of unicast MAC filters would sometime have side-effect
         of corrupting the MAC filters configred for a device.
      It also contains fixes for future qed* drivers that *hopefully* would be
      sent for review in the near future.
      
      In addition, it would allow driver some new functionality, including:
       - Allowing PF/VF driver compaitibility with old drivers [running
         pre-8.10.5.0 firmware].
       - Better debug facilities.
      
      This would also bump the qed* driver versions to 8.10.9.20.
      Signed-off-by: NYuval Mintz <Yuval.Mintz@qlogic.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      05fafbfb
  22. 19 8月, 2016 1 次提交
  23. 09 8月, 2016 1 次提交
  24. 20 6月, 2016 1 次提交
  25. 09 6月, 2016 1 次提交
  26. 04 6月, 2016 2 次提交
  27. 03 6月, 2016 1 次提交
    • Y
      qed: Utilize FW 8.10.3.0 · 351a4ded
      Yuval Mintz 提交于
      The New QED firmware contains several fixes, including:
        - Wrong classification of packets in 4-port devices.
        - Anti-spoof interoperability with encapsulated packets.
        - Tx-switching of encapsulated packets.
      It also slightly improves Tx performance of the device.
      
      In addition, this firmware contains the necessary logic for
      supporting iscsi & rdma, for which we plan on pushing protocol
      drivers in the imminent future.
      Signed-off-by: NYuval Mintz <Yuval.Mintz@qlogic.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      351a4ded