1. 28 6月, 2012 2 次提交
  2. 03 6月, 2012 1 次提交
  3. 25 5月, 2012 6 次提交
    • S
      doc: ext3: update documentation with barrier=1 default · 21848d08
      Stefan Hajnoczi 提交于
      Commit 00eacd66 ("ext3: make ext3 mount default to barrier=1") changed
      the default barrier mount option for ext3.  The documentation needs to
      be updated, so this patch does that.
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Acked-by: NRob Landley <rob@landley.net>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      21848d08
    • M
      Documentation/initrd.txt: Change the location of util-linux · 76dab97c
      Marcos Paulo de Souza 提交于
      The address of util-linux seems deprecated. The new util-linux location is
      in the kernel.org. So, change this for the correct address.
      Signed-off-by: NMarcos Paulo de Souza <marcos.souza.org@gmail.com>
      Acked-by: NRob Landley <rob@landley.net>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      76dab97c
    • M
      Documentation/SubmittingPatches: suggested the use of scripts/get_maintainer.pl · e52d2e1f
      Michel Machado 提交于
      Had I found a reference to scripts/get_maintainer.pl when I first read
      Documentation/SubmittingPatches, it would've saved me some time.
      Signed-off-by: NMichel Machado <michel@digirati.com.br>
      Acked-by: NRob Landley <rob@landley.net>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      e52d2e1f
    • S
      Documentation/kernel-parameters: remove autotest and mcatest · 9b170dbd
      Sebastian Andrzej Siewior 提交于
      It has no more users, the last one is gone in "[PATCH] ia64: Kconfig
      cleanup" aka ("6fd79ab50b").
      mcatest is gone in commit "[PATCH] ia64: SGI SN update"
      ("c6bacd5010ec").
      
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Signed-off-by: NSebastian Andrzej Siewior <sebastian@breakpoint.cc>
      Acked-by: NRob Landley <rob@landley.net>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      9b170dbd
    • D
      dma-buf: add initial vmap documentation · b25b086d
      Dave Airlie 提交于
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      Signed-off-by: NSumit Semwal <sumit.semwal@linaro.org>
      b25b086d
    • D
      dma-buf: mmap support · 4c78513e
      Daniel Vetter 提交于
      Compared to Rob Clark's RFC I've ditched the prepare/finish hooks
      and corresponding ioctls on the dma_buf file. The major reason for
      that is that many people seem to be under the impression that this is
      also for synchronization with outstanding asynchronous processsing.
      I'm pretty massively opposed to this because:
      
      - It boils down reinventing a new rather general-purpose userspace
        synchronization interface. If we look at things like futexes, this
        is hard to get right.
      - Furthermore a lot of kernel code has to interact with this
        synchronization primitive. This smells a look like the dri1 hw_lock,
        a horror show I prefer not to reinvent.
      - Even more fun is that multiple different subsystems would interact
        here, so we have plenty of opportunities to create funny deadlock
        scenarios.
      
      I think synchronization is a wholesale different problem from data
      sharing and should be tackled as an orthogonal problem.
      
      Now we could demand that prepare/finish may only ensure cache
      coherency (as Rob intended), but that runs up into the next problem:
      We not only need mmap support to facilitate sw-only processing nodes
      in a pipeline (without jumping through hoops by importing the dma_buf
      into some sw-access only importer), which allows for a nicer
      ION->dma-buf upgrade path for existing Android userspace. We also need
      mmap support for existing importing subsystems to support existing
      userspace libraries. And a loot of these subsystems are expected to
      export coherent userspace mappings.
      
      So prepare/finish can only ever be optional and the exporter /needs/
      to support coherent mappings. Given that mmap access is always
      somewhat fallback-y in nature I've decided to drop this optimization,
      instead of just making it optional. If we demonstrate a clear need for
      this, supported by benchmark results, we can always add it in again
      later as an optional extension.
      
      Other differences compared to Rob's RFC is the above mentioned support
      for mapping a dma-buf through facilities provided by the importer.
      Which results in mmap support no longer being optional.
      
      Note that this dma-buf mmap patch does _not_ support every possible
      insanity an existing subsystem could pull of with mmap: Because it
      does not allow to intercept pagefaults and shoot down ptes importing
      subsystems can't add some magic of their own at these points (e.g. to
      automatically synchronize with outstanding rendering or set up some
      special resources). I've done a cursory read through a few mmap
      implementions of various subsytems and I'm hopeful that we can avoid
      this (and the complexity it'd bring with it).
      
      Additonally I've extended the documentation a bit to explain the hows
      and whys of this mmap extension.
      
      In case we ever want to add support for explicitly cache maneged
      userspace mmap with a prepare/finish ioctl pair, we could specify that
      userspace needs to mmap a different part of the dma_buf, e.g. the
      range starting at dma_buf->size up to dma_buf->size*2. This works
      because the size of a dma_buf is invariant over it's lifetime. The
      exporter would obviously need to fall back to coherent mappings for
      both ranges if a legacy clients maps the coherent range and the
      architecture cannot suppor conflicting caching policies. Also, this
      would obviously be optional and userspace needs to be able to fall
      back to coherent mappings.
      
      v2:
      - Spelling fixes from Rob Clark.
      - Compile fix for !DMA_BUF from Rob Clark.
      - Extend commit message to explain how explicitly cache managed mmap
        support could be added later.
      - Extend the documentation with implementations notes for exporters
        that need to manually fake coherency.
      
      v3:
      - dma_buf pointer initialization goof-up noticed by Rebecca Schultz
        Zavin.
      
      Cc: Rob Clark <rob.clark@linaro.org>
      Cc: Rebecca Schultz Zavin <rebecca@android.com>
      Acked-by: NRob Clark <rob.clark@linaro.org>
      Signed-Off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: NSumit Semwal <sumit.semwal@linaro.org>
      4c78513e
  4. 23 5月, 2012 6 次提交
  5. 22 5月, 2012 4 次提交
  6. 21 5月, 2012 6 次提交
  7. 20 5月, 2012 9 次提交
  8. 19 5月, 2012 2 次提交
  9. 18 5月, 2012 4 次提交
    • P
      MCA: delete all remaining traces of microchannel bus support. · bb8187d3
      Paul Gortmaker 提交于
      Hardware with MCA bus is limited to 386 and 486 class machines
      that are now 20+ years old and typically with less than 32MB
      of memory.  A quick search on the internet, and you see that
      even the MCA hobbyist/enthusiast community has lost interest
      in the early 2000 era and never really even moved ahead from
      the 2.4 kernels to the 2.6 series.
      
      This deletes anything remaining related to CONFIG_MCA from core
      kernel code and from the x86 architecture.  There is no point in
      carrying this any further into the future.
      
      One complication to watch for is inadvertently scooping up
      stuff relating to machine check, since there is overlap in
      the TLA name space (e.g. arch/x86/boot/mca.c).
      
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: James Bottomley <JBottomley@Parallels.com>
      Cc: x86@kernel.org
      Acked-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NH. Peter Anvin <hpa@zytor.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      bb8187d3
    • P
      scsi: delete the MCA specific drivers and driver code · a88dc06c
      Paul Gortmaker 提交于
      The support for CONFIG_MCA is being removed, since the 20
      year old hardware simply isn't capable of meeting today's
      software demands on CPU and memory resources.
      
      This commit removes the MCA specific SCSI drivers, and the
      MCA specific portions of code in dual role ISA/MCA drivers.
      Also, the MCA specific SCSI documentation is removed.
      
      Cc: James Bottomley <JBottomley@parallels.com>
      Cc: linux-scsi@vger.kernel.org
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      a88dc06c
    • P
      serial: delete the MCA specific 8250 support. · d157be85
      Paul Gortmaker 提交于
      The support for CONFIG_MCA is being removed, since the 20
      year old hardware simply isn't capable of meeting today's
      software demands on CPU and memory resources.
      
      This commit removes the MCA specific 8250 UART code.
      
      Cc: Alan Cox <alan@linux.intel.com>
      Cc: linux-serial@vger.kernel.org
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      d157be85
    • P
      drivers/net: delete all code/drivers depending on CONFIG_MCA · a5e371f6
      Paul Gortmaker 提交于
      The support for CONFIG_MCA is being removed, since the 20
      year old hardware simply isn't capable of meeting today's
      software demands on CPU and memory resources.
      
      This commit removes any MCA specific net drivers, and removes
      any MCA specific probe/support code from drivers that were
      doing a dual ISA/MCA role.
      
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: netdev@vger.kernel.org
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      a5e371f6