1. 30 4月, 2008 1 次提交
  2. 22 10月, 2007 1 次提交
  3. 12 2月, 2007 1 次提交
    • A
      [PATCH] Switch s390 to NO_IOMEM · 23db764d
      Al Viro 提交于
      Martin Schwidefsky wrote:
        "s390 does not even need (in|out)b(_p|).  I wondered what else from
         io.h do we not need.  The answer is: almost nothing.  With the devres
         patch from Al and the dma-mapping patch from Heiko we can get rid of
         iomem and all associated definitions."
      
      So we'll just need to replace NO_IOPORT with NO_IOMEM in Kconfig and
      kill arch/s390/mm/ioremap.c.
      
      BTW, there's an annoying bit of junk in there - IO_SPACE_LIMIT.  We
      only need it for /proc/ioports, which AFAICS shouldn't even be there
      on s390 (or uml).  OTOH, removing that thing would mean a user-visible
      change - we go from "empty file in /proc" to "no such file in /proc"...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      23db764d
  4. 08 12月, 2006 1 次提交
    • H
      [S390] Virtual memmap for s390. · f4eb07c1
      Heiko Carstens 提交于
      Virtual memmap support for s390. Inspired by the ia64 implementation.
      
      Unlike ia64 we need a mechanism which allows us to dynamically attach
      shared memory regions.
      These memory regions are accessed via the dcss device driver. dcss
      implements the 'direct_access' operation, which requires struct pages
      for every single shared page.
      Therefore this implementation provides an interface to attach/detach
      shared memory:
      
      int add_shared_memory(unsigned long start, unsigned long size);
      int remove_shared_memory(unsigned long start, unsigned long size);
      
      The purpose of the add_shared_memory function is to add the given
      memory range to the 1:1 mapping and to make sure that the
      corresponding range in the vmemmap is backed with physical pages.
      It also initialises the new struct pages.
      
      remove_shared_memory in turn only invalidates the page table
      entries in the 1:1 mapping. The page tables and the memory used for
      struct pages in the vmemmap are currently not freed. They will be
      reused when the next segment will be attached.
      Given that the maximum size of a shared memory region is 2GB and
      in addition all regions must reside below 2GB this is not too much of
      a restriction, but there is room for improvement.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      f4eb07c1
  5. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4