1. 20 10月, 2014 1 次提交
  2. 16 10月, 2014 2 次提交
  3. 09 10月, 2014 2 次提交
  4. 10 7月, 2014 1 次提交
  5. 08 2月, 2014 1 次提交
  6. 15 11月, 2013 1 次提交
  7. 10 10月, 2013 1 次提交
  8. 07 6月, 2013 1 次提交
  9. 30 5月, 2013 1 次提交
  10. 08 1月, 2013 2 次提交
  11. 09 10月, 2012 1 次提交
    • K
      mm: kill vma flag VM_RESERVED and mm->reserved_vm counter · 314e51b9
      Konstantin Khlebnikov 提交于
      A long time ago, in v2.4, VM_RESERVED kept swapout process off VMA,
      currently it lost original meaning but still has some effects:
      
       | effect                 | alternative flags
      -+------------------------+---------------------------------------------
      1| account as reserved_vm | VM_IO
      2| skip in core dump      | VM_IO, VM_DONTDUMP
      3| do not merge or expand | VM_IO, VM_DONTEXPAND, VM_HUGETLB, VM_PFNMAP
      4| do not mlock           | VM_IO, VM_DONTEXPAND, VM_HUGETLB, VM_PFNMAP
      
      This patch removes reserved_vm counter from mm_struct.  Seems like nobody
      cares about it, it does not exported into userspace directly, it only
      reduces total_vm showed in proc.
      
      Thus VM_RESERVED can be replaced with VM_IO or pair VM_DONTEXPAND | VM_DONTDUMP.
      
      remap_pfn_range() and io_remap_pfn_range() set VM_IO|VM_DONTEXPAND|VM_DONTDUMP.
      remap_vmalloc_range() set VM_DONTEXPAND | VM_DONTDUMP.
      
      [akpm@linux-foundation.org: drivers/vfio/pci/vfio_pci.c fixup]
      Signed-off-by: NKonstantin Khlebnikov <khlebnikov@openvz.org>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Carsten Otte <cotte@de.ibm.com>
      Cc: Chris Metcalf <cmetcalf@tilera.com>
      Cc: Cyrill Gorcunov <gorcunov@openvz.org>
      Cc: Eric Paris <eparis@redhat.com>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Hugh Dickins <hughd@google.com>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: James Morris <james.l.morris@oracle.com>
      Cc: Jason Baron <jbaron@redhat.com>
      Cc: Kentaro Takeda <takedakn@nttdata.co.jp>
      Cc: Matt Helsley <matthltc@us.ibm.com>
      Cc: Nick Piggin <npiggin@kernel.dk>
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Robert Richter <robert.richter@amd.com>
      Cc: Suresh Siddha <suresh.b.siddha@intel.com>
      Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
      Cc: Venkatesh Pallipadi <venki@google.com>
      Acked-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      314e51b9
  12. 17 8月, 2012 1 次提交
  13. 27 2月, 2012 2 次提交
    • I
      carma-fpga: fix race between data dumping and DMA callback · 6c15d7af
      Ira Snyder 提交于
      When the system is under heavy load, we occasionally saw a problem where
      the system would get a legitimate interrupt when they should be
      disabled.
      
      This was caused by the data_dma_cb() DMA callback unconditionally
      re-enabling FPGA interrupts even when data dumping is disabled. When
      data dumping was re-enabled, the irq handler would fire while a DMA was
      in progress. The "BUG_ON(priv->inflight != NULL);" during the second
      invocation of the DMA callback caused the system to crash.
      
      To fix the issue, the priv->enabled boolean is moved under the
      protection of the priv->lock spinlock. The DMA callback checks the
      boolean to know whether to re-enable FPGA interrupts before it returns.
      
      Now that it is fixed, the driver keeps FPGA interrupts disabled when it
      expects that they are disabled, fixing the bug.
      Signed-off-by: NIra W. Snyder <iws@ovro.caltech.edu>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      6c15d7af
    • I
      carma-fpga: fix lockdep warning · 75ff85a8
      Ira Snyder 提交于
      Lockdep occasionally complains with the message:
      INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
      
      This is caused by calling videobuf_dma_unmap() under spin_lock_irq(). To
      fix the warning, we drop the lock before unmapping and freeing the
      buffer.
      Signed-off-by: NIra W. Snyder <iws@ovro.caltech.edu>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      75ff85a8
  14. 25 1月, 2012 1 次提交
  15. 16 11月, 2011 1 次提交
  16. 31 10月, 2011 1 次提交
  17. 19 5月, 2011 2 次提交
    • I
      misc: Add CARMA DATA-FPGA Programmer support · 0e1d715b
      Ira Snyder 提交于
      This adds support for programming the data processing FPGAs on the OVRO
      CARMA board. These FPGAs have a special programming sequence that
      requires that we program the Freescale DMA engine, which is only
      available inside the kernel.
      Signed-off-by: NIra W. Snyder <iws@ovro.caltech.edu>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      0e1d715b
    • I
      misc: Add CARMA DATA-FPGA Access Driver · c186f0e1
      Ira Snyder 提交于
      This driver allows userspace to access the data processing FPGAs on the
      OVRO CARMA board. It has two modes of operation:
      
      1) random access
      
      This allows users to poke any DATA-FPGA registers by using mmap to map
      the address region directly into their memory map.
      
      2) correlation dumping
      
      When correlating, the DATA-FPGA's have special requirements for getting
      the data out of their memory before the next correlation. This nominally
      happens at 64Hz (every 15.625ms). If the data is not dumped before the
      next correlation, data is lost.
      
      The data dumping driver handles buffering up to 1 second worth of
      correlation data from the FPGAs. This lowers the realtime scheduling
      requirements for the userspace process reading the device.
      Signed-off-by: NIra W. Snyder <iws@ovro.caltech.edu>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      c186f0e1
新手
引导
客服 返回
顶部