1. 08 May, 2007 1 commit
    • Christoph Hellwig's avatar
      move die notifier handling to common code · 1eeb66a1
      Christoph Hellwig authored
      
      
      This patch moves the die notifier handling to common code.  Previous
      various architectures had exactly the same code for it.  Note that the new
      code is compiled unconditionally, this should be understood as an appel to
      the other architecture maintainer to implement support for it aswell (aka
      sprinkling a notify_die or two in the proper place)
      
      arm had a notifiy_die that did something totally different, I renamed it to
      arm_notify_die as part of the patch and made it static to the file it's
      declared and used at.  avr32 used to pass slightly less information through
      this interface and I brought it into line with the other architectures.
      
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix vmalloc_sync_all bustage]
      [bryan.wu@analog.com: fix vmalloc_sync_all in nommu]
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Cc: <linux-arch@vger.kernel.org>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Signed-off-by: default avatarBryan Wu <bryan.wu@analog.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      1eeb66a1
  2. 03 May, 2007 1 commit
  3. 21 Apr, 2007 2 commits
  4. 14 Feb, 2007 1 commit
  5. 06 Feb, 2007 1 commit
    • Russell King's avatar
      [ARM] Move processor_modes[] to .../process.c · ae0a846e
      Russell King authored
      
      
      bad_mode() currently prints the mode which caused the exception, and
      then causes an oops dump to be printed which again displays this
      information (since the CPSR in the struct pt_regs is correct.)  This
      leads to processor_modes[] being shared between traps.c and process.c
      with a local declaration of it.
      
      We can clean this up by moving processor_modes[] to process.c and
      removing the duplication, resulting in processor_modes[] becoming
      static.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      ae0a846e
  6. 06 Jan, 2007 1 commit
  7. 07 Dec, 2006 1 commit
    • Nicolas Pitre's avatar
      [ARM] 3983/2: remove unused argument to __bug() · 7174d852
      Nicolas Pitre authored
      It appears that include/asm-arm/bug.h requires include/linux/stddef.h
      for the definition of NULL. It seems that stddef.h was always included
      indirectly in most cases, and that issue was properly fixed a while ago.
      
      Then commit 5047f09b incorrectly reverted
      change from commit ff10952a
      
       (bad dwmw2)
      and the problem recently resurfaced.
      
      Because the third argument to __bug() is never used anyway, RMK suggested
      getting rid of it entirely instead of readding #include <linux/stddef.h>
      which this patch does.
      Signed-off-by: default avatarNicolas Pitre <nico@cam.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      7174d852
  8. 20 Sep, 2006 1 commit
    • Daniel Jacobowitz's avatar
      [ARM] 3759/2: Remove uses of %? · 6a39dd62
      Daniel Jacobowitz authored
      
      
      Patch from Daniel Jacobowitz
      
      The ARM kernel has several uses of asm("foo%?").  %? is a GCC internal
      modifier used to output conditional execution predicates.  However, no
      version of GCC supports conditionalizing asm statements.  GCC 4.2 will
      correctly expand %? to the empty string in user asms.  Earlier versions may
      reuse the condition from the previous instruction.  In 'if (foo) asm
      ("bar%?");' this is somewhat likely to be right... but not reliable.
      
      So, the only safe thing to do is to remove the uses of %?.  I believe
      the tlbflush.h occurances were supposed to be removed before, based
      on the comment about %? not working at the top of that file.
      
      Old versions of GCC could omit branches around user asms if the asm didn't
      mark the condition codes as clobbered.  This problem hasn't been seen on any
      recent (3.x or 4.x) GCC, but it could theoretically happen.  So, where
      %? was removed a cc clobber was added.
      Signed-off-by: default avatarDaniel Jacobowitz <dan@codesourcery.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      6a39dd62
  9. 14 Aug, 2006 1 commit
    • Horms's avatar
      [PATCH] Change panic_on_oops message to "Fatal exception" · 012c437d
      Horms authored
      
      
      Previously the message was "Fatal exception: panic_on_oops", as introduced
      in a recent patch whith removed a somewhat dangerous call to ssleep() in
      the panic_on_oops path.  However, Paul Mackerras suggested that this was
      somewhat confusing, leadind people to believe that it was panic_on_oops
      that was the root cause of the fatal exception.  On his suggestion, this
      patch changes the message to simply "Fatal exception".  A suitable oops
      message should already have been displayed.
      Signed-off-by: default avatarSimon Horman <horms@verge.net.au>
      Cc: Paul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      012c437d
  10. 31 Jul, 2006 1 commit
    • Horms's avatar
      [PATCH] panic_on_oops: remove ssleep() · cea6a4ba
      Horms authored
      
      
      This patch is part of an effort to unify the panic_on_oops behaviour across
      all architectures that implement it.
      
      It was pointed out to me by Andi Kleen that if an oops has occured in
      interrupt context, then calling sleep() in the oops path will only cause a
      panic, and that it would be really better for it not to be in the path at
      all.
      
      This patch removes the ssleep() call and reworks the console message
      accordinly.  I have a slght concern that the resulting console message is
      too long, feedback welcome.
      
      For powerpc it also unifies the 32bit and 64bit behaviour.
      
      Fror x86_64, this patch only updates the console message, as ssleep() is
      already not present.
      Signed-off-by: default avatarHorms <horms@verge.net.au>
      Acked-by: default avatarPaul Mackerras <paulus@samba.org>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Chris Zankel <chris@zankel.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      cea6a4ba
  11. 30 Jun, 2006 1 commit
  12. 27 Mar, 2006 1 commit
  13. 25 Mar, 2006 1 commit
  14. 22 Feb, 2006 1 commit
  15. 14 Jan, 2006 1 commit
    • Nicolas Pitre's avatar
      [ARM] 3105/4: ARM EABI: new syscall entry convention · 3f2829a3
      Nicolas Pitre authored
      
      
      Patch from Nicolas Pitre
      
      For a while we wanted to change the way syscalls were called on ARM.
      Instead of encoding the syscall number in the swi instruction which
      requires reading back the instruction from memory to extract that number
      and polluting the data cache, it was decided that simply storing the
      syscall number into r7 would be more efficient. Since this represents
      an ABI change then making that change at the same time as EABI support
      is the right thing to do.
      
      It is now expected that EABI user space binaries put the syscall number
      into r7 and use "swi 0" to call the kernel. Syscall register argument
      are also expected to have "EABI arrangement" i.e. 64-bit arguments
      should be put in a pair of registers from an even register number.
      
      Example with long ftruncate64(unsigned int fd, loff_t length):
      
      	legacy ABI:
      	- put fd into r0
      	- put length into r1-r2
      	- use "swi #(0x900000 + 194)" to call the kernel
      
      	new ARM EABI:
      	- put fd into r0
      	- put length into r2-r3 (skipping over r1)
      	- put 194 into r7
      	- use "swi 0" to call the kernel
      
      Note that it is important to use 0 for the swi argument as backward
      compatibility with legacy ABI user space relies on this.
      The syscall macros in asm-arm/unistd.h were also updated to support
      both ABIs and implement the right call method automatically.
      Signed-off-by: default avatarNicolas Pitre <nico@cam.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      3f2829a3
  16. 12 Jan, 2006 2 commits
  17. 03 Jan, 2006 1 commit
    • Russell King's avatar
      [ARM] Cleanup ARM includes · 78ff18a4
      Russell King authored
      
      
      arch/arm/kernel/entry-armv.S has contained a comment suggesting
      that asm/hardware.h and asm/arch/irqs.h should be moved into the
      asm/arch/entry-macro.S include.  So move the includes to these
      two files as required.
      
      Add missing includes (asm/hardware.h, asm/io.h) to asm/arch/system.h
      includes which use those facilities, and remove asm/io.h from
      kernel/process.c.
      
      Remove other unnecessary includes from arch/arm/kernel, arch/arm/mm
      and arch/arm/mach-footbridge.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      78ff18a4
  18. 30 Oct, 2005 2 commits
    • Russell King's avatar
      [ARM] Re-organise die() · d362979a
      Russell King authored
      
      
      Provide __die() which can be called from various contexts to provide
      an oops report.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      d362979a
    • Hugh Dickins's avatar
      [PATCH] mm: arm ready for split ptlock · 69b04754
      Hugh Dickins authored
      
      
      Prepare arm for the split page_table_lock: three issues.
      
      Signal handling's preserve and restore of iwmmxt context currently involves
      reading and writing that context to and from user space, while holding
      page_table_lock to secure the user page(s) against kswapd.  If we split the
      lock, then the structure might span two pages, secured by to read into and
      write from a kernel stack buffer, copying that out and in without locking (the
      structure is 160 bytes in size, and here we're near the top of the kernel
      stack).  Or would the overhead be noticeable?
      
      arm_syscall's cmpxchg emulation use pte_offset_map_lock, instead of
      pte_offset_map and mm-wide page_table_lock; and strictly, it should now also
      take mmap_sem before descending to pmd, to guard against another thread
      munmapping, and the page table pulled out beneath this thread.
      
      Updated two comments in fault-armv.c.  adjust_pte is interesting, since its
      modification of a pte in one part of the mm depends on the lock held when
      calling update_mmu_cache for a pte in some other part of that mm.  This can't
      be done with a split page_table_lock (and we've already taken the lowest lock
      in the hierarchy here): so we'll have to disable split on arm, unless
      CONFIG_CPU_CACHE_VIPT to ensures adjust_pte never used.
      Signed-off-by: default avatarHugh Dickins <hugh@veritas.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      69b04754
  19. 28 Oct, 2005 1 commit
  20. 04 Oct, 2005 1 commit
  21. 21 Sep, 2005 1 commit
  22. 24 Aug, 2005 1 commit
  23. 16 Jul, 2005 1 commit
  24. 30 Jun, 2005 1 commit
  25. 22 Jun, 2005 1 commit
  26. 08 Jun, 2005 1 commit
  27. 05 May, 2005 2 commits
  28. 29 Apr, 2005 1 commit
    • Nicolas Pitre's avatar
      [PATCH] ARM: 2651/3: kernel helpers for NPTL support · 2d2669b6
      Nicolas Pitre authored
      
      
      Patch from Nicolas Pitre
      
      This patch entirely reworks the kernel assistance for NPTL on ARM.
      In particular this provides an efficient way to retrieve the TLS
      value and perform atomic operations without any instruction emulation
      nor special system call.  This even allows for pre ARMv6 binaries to
      be forward compatible with SMP systems without any penalty.
      The problematic and performance critical operations are performed
      through segment of kernel provided user code reachable from user space
      at a fixed address in kernel memory.  Those fixed entry points are
      within the vector page so we basically get it for free as no extra
      memory page is required and nothing else may be mapped at that
      location anyway.
      This is different from (but doesn't preclude) a full blown VDSO
      implementation, however a VDSO would prevent some assembly tricks with
      constants that allows for efficient branching to those code segments.
      And since those code segments only use a few cycles before returning to
      user code, the overhead of a VDSO far call would add a significant
      overhead to such minimalistic operations.
      The ARM_NR_set_tls syscall also changed number.  This is done for two
      reasons:
      1) this patch changes the way the TLS value was previously meant to be
         retrieved, therefore we ensure whatever library using the old way
         gets fixed (they only exist in private tree at the moment since the
         NPTL work is still progressing).
      2) the previous number was allocated in a range causing an undefined
         instruction trap on kernels not supporting that syscall and it was
         determined that allocating it in a range returning -ENOSYS would be
         much nicer for libraries trying to determine if the feature is
         present or not.
      
      Signed-off-by: Nicolas Pitre
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      2d2669b6
  29. 26 Apr, 2005 1 commit
  30. 17 Apr, 2005 1 commit
  31. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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