1. 23 2月, 2010 1 次提交
  2. 13 2月, 2010 1 次提交
  3. 19 11月, 2009 1 次提交
  4. 01 9月, 2009 1 次提交
  5. 06 7月, 2009 1 次提交
  6. 18 5月, 2009 2 次提交
  7. 05 5月, 2009 1 次提交
  8. 16 4月, 2009 1 次提交
  9. 22 1月, 2009 1 次提交
  10. 13 1月, 2009 1 次提交
  11. 07 1月, 2009 1 次提交
    • S
      ibmveth: use consistent types · ff5bfc35
      Stephen Rothwell 提交于
      These variables are only used with an interface that just dumps their
      values into registers to be passed to the hypervisor. The arguments
      to that interface are declared to be "unsigned long", so make these
      variables match.  The macros are only used with these variables, so make
      them match as well.
      
      This code is currently only built for 64bit powerpc, so the transformation
      is really a noop.  If the interface was ever ported to 32 bit, it would
      almost certainly still use registers to pass the parameters and so
      "unsigned long" would still be appropriate.
      Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ff5bfc35
  12. 29 12月, 2008 1 次提交
  13. 23 12月, 2008 1 次提交
  14. 13 11月, 2008 1 次提交
    • W
      netdevice: safe convert to netdev_priv() #part-2 · 4cf1653a
      Wang Chen 提交于
      We have some reasons to kill netdev->priv:
      1. netdev->priv is equal to netdev_priv().
      2. netdev_priv() wraps the calculation of netdev->priv's offset, obviously
         netdev_priv() is more flexible than netdev->priv.
      But we cann't kill netdev->priv, because so many drivers reference to it
      directly.
      
      This patch is a safe convert for netdev->priv to netdev_priv(netdev).
      Since all of the netdev->priv is only for read.
      But it is too big to be sent in one mail.
      I split it to 4 parts and make every part smaller than 100,000 bytes,
      which is max size allowed by vger.
      Signed-off-by: NWang Chen <wangchen@cn.fujitsu.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4cf1653a
  15. 04 11月, 2008 1 次提交
  16. 28 10月, 2008 1 次提交
  17. 27 8月, 2008 1 次提交
    • S
      ibmveth: fix bad UDP checksums · 45e15bb7
      Santiago Leon 提交于
      This patch fixes a ibmveth bug where bad UDP checksums are being transmitted
      when checksum offloading is enabled.
      The hypervisor does checksum offloading only on TCP packets, so ibmveth calls
      skb_checksum_help() for any other protocol.  The bug happens because
      the packet is being modified after the DMA map, so we would need a memory
      barrier before making the hypervisor call.  Reordering the code so that the
      DMA map happens after skb_checksum_help() has the additional advantage of
      fixing a DMA map leak if skb_checksum_help() where to fail.
      Signed-off-by: NSantiago Leon <santil@us.ibm.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      45e15bb7
  18. 28 7月, 2008 1 次提交
    • S
      ibmveth: Fix multiple errors with dma_mapping_error conversion · c713e7cb
      Stephen Rothwell 提交于
      The addition of an argument to dma_mapping_error() in commit
      8d8bb39b "dma-mapping: add the device
      argument to dma_mapping_error()" left a bit of fallout:
      
      drivers/net/ibmveth.c:263: error: too few arguments to function 'dma_mapping_error'
      drivers/net/ibmveth.c:264: error: expected ')' before 'goto'
      drivers/net/ibmveth.c:284: error: expected expression before '}' token
      drivers/net/ibmveth.c:297: error: too few arguments to function 'dma_mapping_error'
      drivers/net/ibmveth.c:298: error: expected ')' before 'dma_unmap_single'
      drivers/net/ibmveth.c:306: error: expected expression before '}' token
      drivers/net/ibmveth.c:491: error: too few arguments to function 'dma_mapping_error'
      drivers/net/ibmveth.c:927: error: too few arguments to function 'dma_mapping_error'
      drivers/net/ibmveth.c:927: error: expected ')' before '{' token
      drivers/net/ibmveth.c:974: error: expected expression before '}' token
      drivers/net/ibmveth.c:914: error: label 'out' used but not defined m
      Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      c713e7cb
  19. 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
  20. 25 7月, 2008 2 次提交
  21. 29 4月, 2008 1 次提交
  22. 19 4月, 2008 1 次提交
  23. 26 3月, 2008 1 次提交
  24. 25 1月, 2008 2 次提交
  25. 13 10月, 2007 1 次提交
  26. 11 10月, 2007 12 次提交