1. 21 3月, 2006 8 次提交
  2. 11 2月, 2006 1 次提交
    • R
      IB/mthca: Don't print debugging info until we have all values · f295c79b
      Roland Dreier 提交于
      When debugging is enabled, the mthca_QUERY_DEV_LIM() firmware command
      function prints out some of the device limits that it queries.
      However the debugging prints happen before all of the fields are
      extracted from the firmware response, so some of the values that get
      printed are uninitialized junk.  Move the prints to the end of the
      function to fix this.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      f295c79b
  3. 31 1月, 2006 2 次提交
    • R
      IB/mthca: Semaphore to mutex conversions · fd9cfdd1
      Roland Dreier 提交于
      Convert semaphores to mutexes in mthca.  Leave firmware command
      interface poll_sem and event_sem as semaphores.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      fd9cfdd1
    • M
      IB/mthca: Don't cancel commands on a signal · e3aa31c5
      Michael S. Tsirkin 提交于
      We have run into the following problem: if a task receives a signal
      while in the process of e.g. destroying a resource (which could be
      because the relevant file was closed) mthca could bail out from trying
      to take a command interface semaphore without performing the
      appropriate command to tell hardware that the resource is being
      destroyed.
      
      As a result we see messages like
       ib_mthca 0000:04:00.0: HW2SW_CQ failed (-4)
      
      In this case, hardware could access the resource after the memory has
      been freed, possibly causing memory corruption.
      
      A simple solution is to replace down_interruptible() by down() in
      command interface activation.
      Signed-off-by: NMichael S. Tsirkin <mst@mellanox.co.il>
      [ It's also not safe to bail out on multicast table operations, since
        they may be invoked on the cleanup path too.  So use down() for
        mcg_table.sem too. ]
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      e3aa31c5
  4. 13 1月, 2006 2 次提交
  5. 01 12月, 2005 1 次提交
  6. 11 11月, 2005 1 次提交
  7. 28 10月, 2005 2 次提交
  8. 18 10月, 2005 1 次提交
  9. 27 9月, 2005 1 次提交
  10. 27 8月, 2005 6 次提交
  11. 28 6月, 2005 2 次提交
  12. 17 4月, 2005 6 次提交