1. 12 2月, 2010 1 次提交
  2. 27 1月, 2010 1 次提交
  3. 10 12月, 2009 1 次提交
  4. 04 12月, 2009 1 次提交
  5. 14 10月, 2009 1 次提交
    • T
      inifiband: Remove BKL from ipath_open() · f96d3015
      Thomas Gleixner 提交于
      cycle_kernel_lock() got pushed down to ipath_open(). I tried hard to
      understand what it might protect, but finally gave up.
      
      Roland noted that qlogic seems to have abandoned the ipath driver and
      came to the following wise conclusion: "So I guess if the BKL stuff is
      blocking you in any way, we can just drop it from ipath and leave it
      as yet another race condition in a rotting old driver."
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      LKML-Reference: <adad44tj090.fsf@cisco.com>
      Cc: Roland Dreier <rdreier@cisco.com>
      f96d3015
  6. 12 10月, 2009 1 次提交
  7. 28 9月, 2009 1 次提交
  8. 21 9月, 2009 1 次提交
  9. 16 9月, 2009 1 次提交
  10. 06 9月, 2009 1 次提交
  11. 09 5月, 2009 1 次提交
  12. 07 4月, 2009 2 次提交
  13. 23 2月, 2009 2 次提交
  14. 19 2月, 2009 1 次提交
    • I
      timers: add mod_timer_pending() · 74019224
      Ingo Molnar 提交于
      Impact: new timer API
      
      Based on an idea from Martin Josefsson with the help of
      Patrick McHardy and Stephen Hemminger:
      
      introduce the mod_timer_pending() API which is a mod_timer()
      offspring that is an invariant on already removed timers.
      
      (regular mod_timer() re-activates non-pending timers.)
      
      This is useful for the networking code in that it can
      allow unserialized mod_timer_pending() timer-forwarding
      calls, but a single del_timer*() will stop the timer
      from being reactivated again.
      
      Also while at it:
      
      - optimize the regular mod_timer() path some more, the
        timer-stat and a debug check was needlessly duplicated
        in __mod_timer().
      
      - make the exports come straight after the function, as
        most other exports in timer.c already did.
      
      - eliminate __mod_timer() as an external API, change the
        users to mod_timer().
      
      The regular mod_timer() code path is not impacted
      significantly, due to inlining optimizations and due to
      the simplifications.
      
      Based-on-patch-from: Stephen Hemminger <shemminger@vyatta.com>
      Acked-by: NStephen Hemminger <shemminger@vyatta.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Patrick McHardy <kaber@trash.net>
      Cc: netdev@vger.kernel.org
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      74019224
  15. 18 1月, 2009 1 次提交
  16. 06 1月, 2009 1 次提交
  17. 30 12月, 2008 1 次提交
  18. 06 12月, 2008 6 次提交
  19. 02 12月, 2008 2 次提交
  20. 28 10月, 2008 1 次提交
  21. 17 10月, 2008 1 次提交
  22. 30 9月, 2008 1 次提交
  23. 21 9月, 2008 1 次提交
  24. 24 8月, 2008 1 次提交
  25. 16 8月, 2008 2 次提交
  26. 05 8月, 2008 1 次提交
    • A
      IB/ipath: Fix printk format warnings · 70117b9e
      Alexander Beregalov 提交于
          ipath_driver.c:1260: warning: format '%Lx' expects type 'long long unsigned int', but argument 6 has type 'long unsigned int'
          ipath_driver.c:1459: warning: format '%Lx' expects type 'long long unsigned int', but argument 4 has type 'u64'
          ipath_intr.c:358: warning: format '%Lx' expects type 'long long unsigned int', but argument 3 has type 'u64'
          ipath_intr.c:358: warning: format '%Lu' expects type 'long long unsigned int', but argument 6 has type 'u64'
          ipath_intr.c:1119: warning: format '%Lx' expects type 'long long unsigned int', but argument 5 has type 'u64'
          ipath_intr.c:1119: warning: format '%Lx' expects type 'long long unsigned int', but argument 3 has type 'u64'
          ipath_intr.c:1123: warning: format '%Lx' expects type 'long long unsigned int', but argument 3 has type 'u64'
          ipath_intr.c:1130: warning: format '%Lx' expects type 'long long unsigned int', but argument 4 has type 'u64'
          ipath_iba7220.c:1032: warning: format '%llx' expects type 'long long unsigned int', but argument 4 has type 'u64'
          ipath_iba7220.c:1045: warning: format '%llX' expects type 'long long unsigned int', but argument 3 has type 'u64'
          ipath_iba7220.c:2506: warning: format '%Lu' expects type 'long long unsigned int', but argument 4 has type 'u64'
      Signed-off-by: NAlexander Beregalov <a.beregalov@gmail.com>
      Cc: Sean Hefty <sean.hefty@intel.com>
      Cc: Hal Rosenstock <hal.rosenstock@gmail.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      70117b9e
  27. 02 8月, 2008 1 次提交
  28. 31 7月, 2008 1 次提交
    • V
      IB/ipath: Use unsigned long for irq flags · 52fd8ca6
      Vegard Nossum 提交于
      A few functions in the ipath driver incorrectly use unsigned int to
      hold irq flags for spin_lock_irqsave().
      
      This patch was generated using the Coccinelle framework with the
      following semantic patch:
      
      The semantic patch I used was this:
      
      @@
      expression lock;
      identifier flags;
      expression subclass;
      @@
      
      - unsigned int flags;
      + unsigned long flags;
      
      ...
      
      <+...
      
      (
       spin_lock_irqsave(lock, flags)
      |
       _spin_lock_irqsave(lock)
      |
       spin_unlock_irqrestore(lock, flags)
      |
       _spin_unlock_irqrestore(lock, flags)
      |
       read_lock_irqsave(lock, flags)
      |
       _read_lock_irqsave(lock)
      |
       read_unlock_irqrestore(lock, flags)
      |
       _read_unlock_irqrestore(lock, flags)
      |
       write_lock_irqsave(lock, flags)
      |
       _write_lock_irqsave(lock)
      |
       write_unlock_irqrestore(lock, flags)
      |
       _write_unlock_irqrestore(lock, flags)
      |
       spin_lock_irqsave_nested(lock, flags, subclass)
      |
       _spin_lock_irqsave_nested(lock, subclass)
      |
       spin_unlock_irqrestore(lock, flags)
      |
       _spin_unlock_irqrestore(lock, flags)
      |
       _raw_spin_lock_flags(lock, flags)
      |
       __raw_spin_lock_flags(lock, flags)
      )
      
      ...+>
      
      Cc: Ralph Campbell <ralph.campbell@qlogic.com>
      Cc: Julia Lawall <julia@diku.dk>
      Cc: Alexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NVegard Nossum <vegard.nossum@gmail.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      52fd8ca6
  29. 27 7月, 2008 1 次提交
    • F
      dma-mapping: add the device argument to dma_mapping_error() · 8d8bb39b
      FUJITA Tomonori 提交于
      Add per-device dma_mapping_ops support for CONFIG_X86_64 as POWER
      architecture does:
      
      This enables us to cleanly fix the Calgary IOMMU issue that some devices
      are not behind the IOMMU (http://lkml.org/lkml/2008/5/8/423).
      
      I think that per-device dma_mapping_ops support would be also helpful for
      KVM people to support PCI passthrough but Andi thinks that this makes it
      difficult to support the PCI passthrough (see the above thread).  So I
      CC'ed this to KVM camp.  Comments are appreciated.
      
      A pointer to dma_mapping_ops to struct dev_archdata is added.  If the
      pointer is non NULL, DMA operations in asm/dma-mapping.h use it.  If it's
      NULL, the system-wide dma_ops pointer is used as before.
      
      If it's useful for KVM people, I plan to implement a mechanism to register
      a hook called when a new pci (or dma capable) device is created (it works
      with hot plugging).  It enables IOMMUs to set up an appropriate
      dma_mapping_ops per device.
      
      The major obstacle is that dma_mapping_error doesn't take a pointer to the
      device unlike other DMA operations.  So x86 can't have dma_mapping_ops per
      device.  Note all the POWER IOMMUs use the same dma_mapping_error function
      so this is not a problem for POWER but x86 IOMMUs use different
      dma_mapping_error functions.
      
      The first patch adds the device argument to dma_mapping_error.  The patch
      is trivial but large since it touches lots of drivers and dma-mapping.h in
      all the architecture.
      
      This patch:
      
      dma_mapping_error() doesn't take a pointer to the device unlike other DMA
      operations.  So we can't have dma_mapping_ops per device.
      
      Note that POWER already has dma_mapping_ops per device but all the POWER
      IOMMUs use the same dma_mapping_error function.  x86 IOMMUs use device
      argument.
      
      [akpm@linux-foundation.org: fix sge]
      [akpm@linux-foundation.org: fix svc_rdma]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix bnx2x]
      [akpm@linux-foundation.org: fix s2io]
      [akpm@linux-foundation.org: fix pasemi_mac]
      [akpm@linux-foundation.org: fix sdhci]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix sparc]
      [akpm@linux-foundation.org: fix ibmvscsi]
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Cc: Muli Ben-Yehuda <muli@il.ibm.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Avi Kivity <avi@qumranet.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8d8bb39b
  30. 22 7月, 2008 1 次提交
  31. 15 7月, 2008 1 次提交
    • R
      IB/ipath: Use IEEE OUI for vendor_id reported by ibv_query_device() · df866619
      Ralph Campbell 提交于
      The IB spe. for SubnGet(NodeInfo) and query HCA says that the vendor
      ID field should be the IEEE OUI assigned to the vendor.  The ipath
      driver was returning the PCI vendor ID instead.  This will affect
      applications which call ibv_query_device().  The old value was
      0x001fc1 or 0x001077, the new value is 0x001175.
      
      The vendor ID doesn't appear to be exported via /sys so that should
      reduce possible compatibility issues.  I'm only aware of Open MPI as a
      major application which depends on this change, and they have made
      necessary adjustments.
      Signed-off-by: NRalph Campbell <ralph.campbell@qlogic.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      df866619