07 Jan, 2006

1 commit

  • Sanitize some s390 Kconfig options. We have ARCH_S390, ARCH_S390X,
    ARCH_S390_31, 64BIT, S390_SUPPORT and COMPAT. Replace these 6 options by
    S390, 64BIT and COMPAT.

    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Schwidefsky
     

09 Nov, 2005

1 commit


07 Nov, 2005

2 commits

  • This is the arch/ part of the big kfree cleanup patch.

    Remove pointless checks for NULL prior to calling kfree() in arch/.

    Signed-off-by: Jesper Juhl
    Acked-by: Grant Grundler
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jesper Juhl
     
  • Remove pagex pseudo page fault code. It does not work together with the
    system call speedup that makes the complete system call path enabled for
    interrupts. To make pagex and the syscall speedup code work together we would
    have to add code to the program check handler to do a critical section cleanup
    like the asynchronous interrupt code. This would make program checks slower.
    Not what we want.

    Newer versions of z/VM have the improved pfault pseudo page fault interface.
    This replaces the old pagex interface and does not have the problem. So its
    better to just rip out the pagex code.

    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Schwidefsky
     

30 Oct, 2005

1 commit

  • First step in pushing down the page_table_lock. init_mm.page_table_lock has
    been used throughout the architectures (usually for ioremap): not to serialize
    kernel address space allocation (that's usually vmlist_lock), but because
    pud_alloc,pmd_alloc,pte_alloc_kernel expect caller holds it.

    Reverse that: don't lock or unlock init_mm.page_table_lock in any of the
    architectures; instead rely on pud_alloc,pmd_alloc,pte_alloc_kernel to take
    and drop it when allocating a new one, to check lest a racing task already
    did. Similarly no page_table_lock in vmalloc's map_vm_area.

    Some temporary ugliness in __pud_alloc and __pmd_alloc: since they also handle
    user mms, which are converted only by a later patch, for now they have to lock
    differently according to whether or not it's init_mm.

    If sources get muddled, there's a danger that an arch source taking
    init_mm.page_table_lock will be mixed with common source also taking it (or
    neither take it). So break the rules and make another change, which should
    break the build for such a mismatch: remove the redundant mm arg from
    pte_alloc_kernel (ppc64 scrapped its distinct ioremap_mm in 2.6.13).

    Exceptions: arm26 used pte_alloc_kernel on user mm, now pte_alloc_map; ia64
    used pte_alloc_map on init_mm, now pte_alloc_kernel; parisc had bad args to
    pmd_alloc and pte_alloc_kernel in unused USE_HPPA_IOREMAP code; ppc64
    map_io_page forgot to unlock on failure; ppc mmu_mapin_ram and ppc64 im_free
    took page_table_lock for no good reason.

    Signed-off-by: Hugh Dickins
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Hugh Dickins
     

05 Sep, 2005

1 commit

  • There is a race in pfault_interrupt. That function gets called two times for
    each pfault notification. Once with a subcode of 0 to indicate that a real
    page is not available and once with a subcode of 0x80 to indicate that the
    page is present again.

    Since the two external interrupts can be delivered on two different cpus the
    order in which the two calls are made is unpredictable. It is possible that
    the subcode 0x80 interrupt is completed before the subcode 0x00 interrupt has
    done the wake_up() call.

    To avoid calling wake_up() on an already removed task structure proper task
    structure reference counting is needed. Increase the reference counter in the
    subcode 0x00 interrupt before setting pfault_wait to zero and return the
    reference after the wake_up call.

    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Schwidefsky
     

26 Jun, 2005

1 commit


22 Jun, 2005

1 commit


05 Jun, 2005

1 commit

  • The condition for no context in do_exception checks for hard and soft
    interrupts by using in_interrupt() but not for preemption. This is bad for
    the users of __copy_from/to_user_inatomic because the fault handler might call
    schedule although the preemption count is != 0. Use in_atomic() instead
    in_interrupt().

    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Schwidefsky
     

01 May, 2005

2 commits

  • An arbitrary guest must not be allowed to trigger cmm actions. Only one
    specific guest namely the one that serves as the resource monitor may send cmm
    messages. Add a parameter that allows to specify the guest that may send
    messages. z/VMs resource manager has the name 'VMRMSVM' which is the default.

    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Schwidefsky
     
  • The memory setup didn't take care of memory holes and this makes the memory
    management think there would be more memory available than there is in
    reality. That causes the OOM killer to kill processes even if there is enough
    memory left that can be written to the swap space.

    The patch fixes this by using free_area_init_node with an array of memory
    holes instead of free_area_init. Further the patch cleans up the code in
    setup.c by splitting setup_arch into smaller pieces.

    Signed-off-by: Martin Schwidefsky

    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Heiko Carstens
     

17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds